| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Shay Rojansky <roji(at)roji(dot)org>, "Pgsql-hackers(at)postgresql(dot)org" <Pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Allow ssl_renegotiation_limit in PG 9.5 |
| Date: | 2015-10-14 17:27:55 |
| Message-ID: | 20151014172755.GC4405@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund wrote:
> On 2015-10-14 14:19:40 -0300, Alvaro Herrera wrote:
> > I think we could continue to have the parameter except that it throws an
> > error if you try to set it to something other than 0.
>
> That'll make it hard to ever remove it tho.
Well, we just have to wait until 9.4 is out of support (so by the time
we're releasing 9.9, or 9.8 if we don't get release cycles under
control). As far as I recall we still have the alias entry for sort_mem
in map_old_guc_names, and what grief does it cause?
> Not sure if it's worth doing so for a dubious use of the variable.
What would you recommend then? Forcing the user to specify the version
before the connection is established is not nice.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amir Rohan | 2015-10-14 17:39:08 | Re: Proposal: pg_confcheck - syntactic & semantic validation of postgresql configuration files |
| Previous Message | Andres Freund | 2015-10-14 17:21:49 | Re: Allow ssl_renegotiation_limit in PG 9.5 |