From: | Jacob Champion <jchampion(at)timescale(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Subject: | Re: [PoC] Let libpq reject unexpected authentication requests |
Date: | 2022-06-30 23:26:54 |
Message-ID: | CAAWbhmiKUFtkzF5_UFrJNssyTh2QEB7qF70K8zC9KWG0jMxmGw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jun 29, 2022 at 6:36 AM Peter Eisentraut
<peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> It's not strictly related to your patch, but maybe this hint has
> outlived its usefulness? I mean, we don't list all available tables
> when you try to reference a table that doesn't exist. And unordered on
> top of that.
Yeah, maybe it'd be better to tell the user the correct context for an
otherwise-valid option ("the 'sslcert' option may only be applied to
USER MAPPING"), and avoid the option dump entirely?
--
v7, attached, fixes configuration on Windows.
--Jacob
Attachment | Content-Type | Size |
---|---|---|
since-v6.diff.txt | text/plain | 1.3 KB |
v7-0002-Add-sslcertmode-option-for-client-certificates.patch | text/x-patch | 18.0 KB |
v7-0001-libpq-let-client-reject-unexpected-auth-methods.patch | text/x-patch | 35.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Bossart | 2022-06-30 23:29:31 | Re: replacing role-level NOINHERIT with a grant-level option |
Previous Message | Jacob Champion | 2022-06-30 23:16:24 | Re: [PATCH] minor reloption regression tests improvement |