Re: Allow ssl_renegotiation_limit in PG 9.5
От | Tom Lane |
---|---|
Тема | Re: Allow ssl_renegotiation_limit in PG 9.5 |
Дата | |
Msg-id | 31025.1444842270@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Allow ssl_renegotiation_limit in PG 9.5 (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: Allow ssl_renegotiation_limit in PG 9.5
|
Список | pgsql-hackers |
Andres Freund <andres@anarazel.de> writes: > On 2015-10-14 18:53:14 +0300, Shay Rojansky wrote: >> However, the new situation where some versions of PG allow this parameter >> while others bomb when seeing it. Specifically, Npgsql sends >> ssl_renegotiation_limit=0 in the startup packet to completely disable >> renegotiation. At this early stage it doesn't know yet whether the database >> it's connecting to is PG 9.5 or earlier. > I find it a rather debatable practice to send such a parameter > unconditionally. Why are you sending it before the connection has even > been established? It doesn't seem to me that a connector such as npgsql has any business whatsoever fooling with such a parameter, unconditionally or otherwise. regards, tom lane
В списке pgsql-hackers по дате отправления: