Re: [PATCH] COPY .. COMPRESSED

From: Greg Stark <stark(at)mit(dot)edu>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] COPY .. COMPRESSED
Date: 2013-01-15 13:35:57
Message-ID: CAM-w4HOH4kAkUvBsM7=fb7=P2A1Mx=vLGEH7Kfj4ZUdGqfenjw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 15, 2013 at 2:33 AM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> * Peter Eisentraut (peter_e(at)gmx(dot)net) wrote:
>> On 1/14/13 11:28 AM, Stephen Frost wrote:
>> > While there is no option currently for having the server do the
>> > compression before sending the data over the wire.
>>
>> OpenSSL?
>
> To be honest, I expected that to come up earlier in this discussion.
> It'd be redundant to use OpenSSL for compression and then ALSO do
> compression on the client side to save into a custom format dump.

For what it's worth there was a security announcement not long ago
that made OpenSSL disable compression in streams by default. I'm not
sure if it's relevant to Postgres or not.

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2013-01-15 13:53:30 Re: another idea for changing global configuration settings from SQL
Previous Message Andres Freund 2013-01-15 13:01:29 Re: logical changeset generation v4