| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robbie Harwood <rharwood(at)redhat(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH v9] GSSAPI encryption support |
| Date: | 2016-03-31 23:19:06 |
| Message-ID: | CAB7nPqQvb-c9AS4z7p8QqGgeBpvX+g=zWGFLtPBvxj=x=EAwyQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Apr 1, 2016 at 6:10 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2016-04-01 00:05:42 | Re: So, can we stop supporting Windows native now? |
| Previous Message | Michael Paquier | 2016-03-31 23:15:14 | Re: Correction for replication slot creation error message in 9.6 |