Horton

Re: [PATCH] Expose port->authn_id to extensions and triggers

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: "Drouvot, Bertrand" <bdrouvot@amazon.com>
Cc: Joe Conway <mail@joeconway.com>, Jacob Champion <jchampion@timescale.com>, Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, "sfrost@snowman.net" <sfrost@snowman.net>, "rjuju123@gmail.com" <rjuju123@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, "andres@anarazel.de" <andres@anarazel.de>
Date: 2022-08-09T09:17:55Z
Lists: pgsql-hackers 
On Mon, Aug 08, 2022 at 12:43:14PM +0200, Drouvot, Bertrand wrote:
> but I'm not sure we should do it as a first step (given the fact that this
> is not Port->authn_id that is passed down to the parallel workers in the
> SYSTEM_USER patch).
> 
> What do you think about working on both (aka a) v11-002 only
> ClientConnectionInfo and b) SYSTEM_USER) in parallel?

It seems to me that completing ClientConnectionInfo first has the
advantage of not having to tweak twice the interface we are going to
use when passing down the full structure to the workers, so I would
choose for doing it first (with one field for the authn, and a second
field for the auth method so as the the workers can build SYSTEM_USER
by themselves when required).
--
Michael

Commits

  1. Remove initialization of MyClientConnectionInfo at backend startup

  2. Allow parallel workers to retrieve some data from Port