Re: [PATCH v9] GSSAPI encryption support
Michael Paquier <michael.paquier@gmail.com>
From: Michael Paquier <michael.paquier@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robbie Harwood <rharwood@redhat.com>,
Alvaro Herrera <alvherre@2ndquadrant.com>, PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Date: 2016-03-31T23:19:06Z
Lists: pgsql-hackers
On Fri, Apr 1, 2016 at 6:10 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > If that's what it is, it seems fairly broken to have it connected up to a > GUC variable. Especially one that's USERSET; some people will wonder why > frobbing it with SET does nothing, and others will bitch that they think > it should be superuser-only or some such. I'd keep it localized to the > connection logic, myself. There's already logic in ProcessStartupPacket > for connection options that aren't GUC variables, so I'd suggest adding > another case there instead of pretending this is a settable GUC variable. Argh, yes right. That's what we should look for. -- Michael
Commits
-
GSSAPI encryption support
- b0b39f72b990 12.0 landed
-
Fix typo
- 57c932475504 9.6.0 cited