From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Radosław Smogura <rsmogura(at)softperience(dot)eu> |
Cc: | PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [Streaming] Datum compression |
Date: | 2011-06-16 13:51:53 |
Message-ID: | 29172.1308232313@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
=?utf-8?q?Rados=C5=82aw_Smogura?= <rsmogura(at)softperience(dot)eu> writes:
> I think about following functionality to add to streaming. In some way earlier
> or later soemone will add possibility for gzip communication. As I try to make
> streaming, I wonder if it is possible to change TOAST compression to
> GZIP/zLib, currently is LZMA.
> I want to make this: if user want to use compression during communication,
> server will be able to send compressed datum, instead of doing recompression.
> GZIP is actually quite popular, and skipping "plain" Windows C, it's supported
> on all driver platforms, including Java and .NET.
> What do You think about this approach.
The fact that TOAST depends on a non-gzip compressor is intentional.
The code that's there is faster than gzip, IIRC, and also there is
no problem with it possibly not being available on a particular system.
You haven't provided any justification that would overrule these
reasons.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2011-06-16 14:05:30 | Re: psql describe.c cleanup |
Previous Message | Robert Creager | 2011-06-16 13:48:42 | Re: Why polecat and colugos are failing to build back branches |