| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SSL renegotiation |
| Date: | 2013-10-01 13:16:02 |
| Message-ID: | 20131001131601.GG5235@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Since back branches releases are getting closer, I would like to push
this to all supported branches. To avoid a compatibility nightmare in
case the new die-on-delayed-renegotiation behavior turns out not to be
so great, I think it would be OK to set the error level to WARNING in
all branches but master (and reset the byte count, to avoid filling the
log). I would also add a CONTEXT line with the current counter value
and the configured limit, and a HINT to report to pg-hackers. That way
we will hopefully have more info on problems in the field.
Anybody opposed to this?
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-10-01 14:17:55 | Re: SSL renegotiation |
| Previous Message | Andrew Dunstan | 2013-09-30 15:38:51 | pgsql: Add missing condition for pg_depend in hstore migration script. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-10-01 13:35:44 | [PATCH] Fix pg_isolation_regress to work outside its build directory |
| Previous Message | David Johnston | 2013-10-01 12:57:22 | Re: Documentation for SET var_name FROM CURRENT |