| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Shay Rojansky <roji(at)roji(dot)org>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "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-17 19:23:11 |
| Message-ID: | FAACE45E-74D5-4499-A688-13472F6708A1@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Oct 17, 2015, at 10:57 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>> Rough patch for the extensible, backpatchable, non-invasive proposal
>> attached.
>
> This just doesn't make any sense. This way npgsql setting that flag can't be released before a new set of backbranch releases are in widespread use. Otherwise it'll just error out in all those, not just in 9.5 as it's now the case. It breaks compatibility with all unsupported versions of postgres because those will never learn to ignore this driver argument. Without any need.
Quite so. Simon's proposal would leave a swath of devastation of exactly the type we're trying to fix, but on an epic scale.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-10-17 20:52:03 | Re: Dangling Client Backend Process |
| Previous Message | Joe Conway | 2015-10-17 18:45:39 | Re: dblink: add polymorphic functions. |