| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Jacob Champion <pchampion(at)vmware(dot)com>, "rjuju123(at)gmail(dot)com" <rjuju123(at)gmail(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 18:56:45 |
| Message-ID: | a1eb50ab-c5c5-f73b-4887-58be739d12a1@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 25.02.22 21:19, Jacob Champion wrote:
> On Fri, 2022-02-25 at 16:28 +0000, Jacob Champion wrote:
>> Ha, opr_sanity caught my use of cstring. I'll work on a fix later
>> today.
>
> Fixed in v3.
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2022-03-01 19:12:59 | Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file |
| Previous Message | Chapman Flack | 2022-03-01 18:55:42 | Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file |