Re: slower connect from hostnossl clients
| От | Magnus Hagander |
|---|---|
| Тема | Re: slower connect from hostnossl clients |
| Дата | |
| Msg-id | CABUevEz5qRmq4EbYsBZ+uJfg_3_ap361ZQtgbH_eF+2j6P0zag@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: slower connect from hostnossl clients (Pavel Stehule <pavel.stehule@gmail.com>) |
| Ответы |
Re: slower connect from hostnossl clients
Re: slower connect from hostnossl clients Re: slower connect from hostnossl clients Re: slower connect from hostnossl clients |
| Список | pgsql-hackers |
On Tue, Jun 7, 2016 at 11:31 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
2016-06-07 11:29 GMT+02:00 Magnus Hagander <magnus@hagander.net>:On Tue, Jun 7, 2016 at 11:24 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote:Is it expected behave?The ssl connection is slower, and it is expected. But when I configure pg_hba.conf to disable ssl via hostnossl, then ssl is not used, but the speed is similar to ssl.HiI am testing speed of connection to Postgres.That's definitely not expected behavior. hostnossl should turn off ssl which should turn off the overhead completely. Does it make a difference if you also disable it from the client side?When I explicitly disabled ssl, then I seen significantly less time
Intersting. Can you check with a network trace that it actually turns off ssl, so nothing is broken there?
One thing that could be taking the time is an extra roundtrip -- e.g. it tries to connect with ssl fails and retries without. A network trace should also make this obvious, and can hopefully show you exactly where in the connection the time is spent.
В списке pgsql-hackers по дате отправления: