On Wed, Jun 24, 2015 at 3:49 PM, Andres Freund <and...@anarazel.de> wrote: > On 2015-06-24 15:41:22 -0400, Peter Eisentraut wrote: >> On 6/24/15 3:13 PM, Andres Freund wrote: >> > Meh. The relevant branches already exist, as you can disable it today. >> > >> > We could also just change the default in the back branches. >> >> One more argument for leaving everything alone. If users don't like it, >> they can turn it off themselves. > > Because it's so obvious to get there from "SSL error: unexpected > message", "SSL error: bad write retry" or "SSL error: unexpected record" > to disabling renegotiation. Right? Search the archives and you'll find > plenty of those, mostly in relation to streaming rep. It took -hackers > years to figure out what causes those, how are normal users supposed to > a) correlate such errors with renegotiation b) evaluate what do about > it?
We could document the issues, create release-note entries suggesting a configuration change, and/or blog about it. I don't accept the argument that there are not ways to tell users about things they might want to do. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
