| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Marko Kreen <markokr(at)gmail(dot)com>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Disable OpenSSL compression |
| Date: | 2011-11-08 14:58:03 |
| Message-ID: | 20555.1320764283@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 11/08/2011 09:34 AM, Tom Lane wrote:
>> There might be some argument for providing a client option to disable
>> compression, but it should not be forced, and it shouldn't even be the
>> default. But before adding YA connection option, I'd want to see some
>> evidence that it's useful over non-local connections.
> I can certainly conceive of situations where one wants SSL on a high
> speed/bandwidth network. I don't think we should assume that all or even
> most real world SSL use will be across slow networks.
Even for that use-case, I don't believe that testing on a local loopback
connection should be considered representative.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-11-08 15:03:13 | Re: Disable OpenSSL compression |
| Previous Message | Andrew Dunstan | 2011-11-08 14:45:30 | Re: Disable OpenSSL compression |