Postgres Pro
Downloads
Home   >   mailing lists

Re: [PATCH] Expose port->authn_id to extensions and triggers - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [PATCH] Expose port->authn_id to extensions and triggers
Date
Msg-id a1eb50ab-c5c5-f73b-4887-58be739d12a1@enterprisedb.com
Whole thread Raw
In response to Re: [PATCH] Expose port->authn_id to extensions and triggers  (Jacob Champion <pchampion@vmware.com>)
Responses Re: [PATCH] Expose port->authn_id to extensions and triggers  (Jacob Champion <pchampion@vmware.com>)
List pgsql-hackers
Tree view 
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.

pgsql-hackers by date:

Previous
From: Chapman Flack
Date:
Subject: Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file
Next
From: Stephen Frost
Date:
Subject: Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file