Re: Disable OpenSSL compression
От | Tom Lane |
---|---|
Тема | Re: Disable OpenSSL compression |
Дата | |
Msg-id | 20073.1320762840@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Disable OpenSSL compression (Marko Kreen <markokr@gmail.com>) |
Ответы |
Re: Disable OpenSSL compression
Re: Disable OpenSSL compression Re: Disable OpenSSL compression Re: Disable OpenSSL compression Re: Disable OpenSSL compression Re: Disable OpenSSL compression |
Список | pgsql-hackers |
Marko Kreen <markokr@gmail.com> writes: > On Tue, Nov 8, 2011 at 3:59 PM, Albe Laurenz <laurenz.albe@wien.gv.at> wrote: >> It is possible that this could cause a performance >> regression for people who SELECT lots of compressible >> data over really slow network connections, but is that >> a realistic scenario? > Yes, it's a realistic scenario. Please make it a option. I distinctly recall us getting bashed a few years ago because there wasn't any convenient way to turn SSL compression *on*. Now that SSL finally does the sane thing by default, you want to turn it off? The fact of the matter is that in most situations where you want SSL, ie links across insecure WANs, compression is a win. Testing a local connection, as you seem to have done, is just about 100% irrelevant to performance in the real world. 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. regards, tom lane
В списке pgsql-hackers по дате отправления: