Re: [PATCH] Expose port->authn_id to extensions and triggers
От | Drouvot, Bertrand |
---|---|
Тема | Re: [PATCH] Expose port->authn_id to extensions and triggers |
Дата | |
Msg-id | 34308245-ea21-82ee-b1fd-00b4766f3527@amazon.com обсуждение исходный текст |
Ответ на | Re: [PATCH] Expose port->authn_id to extensions and triggers (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: [PATCH] Expose port->authn_id to extensions and triggers
|
Список | pgsql-hackers |
Hi, On 8/9/22 11:17 AM, Michael Paquier wrote: > 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). Yeah fair point. Agree that it makes sense to work on those patches in this particular order then. Thanks, -- Bertrand Drouvot Amazon Web Services: https://aws.amazon.com
В списке pgsql-hackers по дате отправления: