From: | Florian Pflug <fgp(at)phlo(dot)org> |
---|---|
To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Euler Taveira <euler(at)timbira(dot)com>, Marko Kreen <markokr(at)gmail(dot)com>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Claes Jakobsson <claes(at)versed(dot)se> |
Subject: | Re: libpq compression |
Date: | 2012-06-25 19:45:26 |
Message-ID: | E52370CE-442F-46CC-BE5F-C7577FFB283F@phlo.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jun25, 2012, at 21:21 , Dimitri Fontaine wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> Or that it takes less code/generates cleaner code...
>
> So we're talking about some LZO things such as snappy from google, and
> that would be another run time dependency IIUC.
>
> I think it's time to talk about fastlz:
>
> http://fastlz.org/
> http://code.google.com/p/fastlz/source/browse/trunk/fastlz.c
>
> 551 lines of C code under MIT license, works also under windows
>
> I guess it would be easy (and safe) enough to embed in our tree should
> we decide going this way.
Agreed. If we extend the protocol to support compression, and not rely
on SSL, then let's pick one of these LZ77-style compressors, and let's
integrate it into our tree.
We should then also make it possible to enable compression only for
the server -> client direction. Since those types of compressions are
usually pretty easy to decompress, that reduces the amount to work
non-libpq clients have to put in to take advantage of compression.
best regards,
Florian Pflug
From | Date | Subject | |
---|---|---|---|
Next Message | Phil Sorber | 2012-06-25 19:49:01 | Re: libpq compression |
Previous Message | Dimitri Fontaine | 2012-06-25 19:21:32 | Re: libpq compression |