| From: | Jacob Champion <pchampion(at)vmware(dot)com> |
|---|---|
| To: | "rjuju123(at)gmail(dot)com" <rjuju123(at)gmail(dot)com>, "peter(dot)eisentraut(at)enterprisedb(dot)com" <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "michael(at)paquier(dot)xyz" <michael(at)paquier(dot)xyz>, "sfrost(at)snowman(dot)net" <sfrost(at)snowman(dot)net> |
| Subject: | Re: [PATCH] Expose port->authn_id to extensions and triggers |
| Date: | 2022-03-01 22:05:37 |
| Message-ID: | 64586c91c87c067dd912a24438570a8b8ccb93e0.camel@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2022-03-01 at 19:56 +0100, Peter Eisentraut wrote:
> This patch contains no documentation. I'm having a hard time
> understanding what the name "session_authn_id" is supposed to convey.
> The comment for the Port.authn_id field says this is the "system
> username", which sounds like a clearer terminology.
"System username" may help from an internal development perspective,
especially as it relates to pg_ident.conf, but I don't think that's
likely to be a useful descriptor to an end user. (I don't think of a
client certificate's Subject Distinguished Name as a "system
username".) Does my attempt in v5 help?
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-03-01 22:35:22 | Re: Consider parallel for lateral subqueries with limit |
| Previous Message | Jacob Champion | 2022-03-01 22:03:20 | Re: [PATCH] Expose port->authn_id to extensions and triggers |