| From: | Jacob Champion <pchampion(at)vmware(dot)com> |
|---|---|
| To: | "sfrost(at)snowman(dot)net" <sfrost(at)snowman(dot)net> |
| Cc: | "rjuju123(at)gmail(dot)com" <rjuju123(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "michael(at)paquier(dot)xyz" <michael(at)paquier(dot)xyz>, "andres(at)anarazel(dot)de" <andres(at)anarazel(dot)de> |
| Subject: | Re: [PATCH] Expose port->authn_id to extensions and triggers |
| Date: | 2022-02-28 21:42:54 |
| Message-ID: | 9450542e69204110ba60da2c035cee3097d1cf02.camel@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 2022-02-28 at 16:00 -0500, Stephen Frost wrote:
> > commit efec9f040843d1de2fc52f5ce0d020478a5bc75d
> > Author: Jacob Champion <pchampion(at)vmware(dot)com>
> > Date: Mon Feb 28 10:28:51 2022 -0800
> >
> > squash! Add API to retrieve authn_id from SQL
>
> Bleh. :) Squash indeed.
Ha, I wasn't sure if anyone read the since-diffs :) I'll start
wordsmithing them more in the future.
> > Subject: [PATCH v4] Add API to retrieve authn_id from SQL
> >
> > The authn_id field in MyProcPort is currently only accessible to the
> > backend itself. Add a SQL function, pg_session_authn_id(), to expose
> > the field to triggers that may want to make use of it.
>
> Only did a quick look but generally looks reasonable to me.
Thanks!
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2022-02-28 21:42:55 | Re: Proposal: Support custom authentication methods using hooks |
| Previous Message | Tom Lane | 2022-02-28 21:18:48 | Re: Proposal: Support custom authentication methods using hooks |