| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, 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 15:03:13 |
| Message-ID: | CA+TgmoZqaMuf323Np6+ggSEQYoVSTY0dfdrun2RRCMfqOew-1Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Nov 8, 2011 at 9:58 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.
Probably not, but I think we ought to provide the option to disable
compression for those who want to do that. I also agree with you that
we should leave the default as-is.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Kreen | 2011-11-08 15:05:46 | Re: Disable OpenSSL compression |
| Previous Message | Tom Lane | 2011-11-08 14:58:03 | Re: Disable OpenSSL compression |