| From: | Jacob Champion <pchampion(at)vmware(dot)com> |
|---|---|
| To: | "michael(at)paquier(dot)xyz" <michael(at)paquier(dot)xyz>, "andres(at)anarazel(dot)de" <andres(at)anarazel(dot)de> |
| Cc: | "rjuju123(at)gmail(dot)com" <rjuju123(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "sfrost(at)snowman(dot)net" <sfrost(at)snowman(dot)net> |
| Subject: | Re: [PATCH] Expose port->authn_id to extensions and triggers |
| Date: | 2022-03-03 19:16:17 |
| Message-ID: | a521eb40f5068d902c821368f2be0c474a3c2aa6.camel@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2022-03-03 at 16:45 +0900, Michael Paquier wrote:
> Anyway, FixedParallelState
> includes some authentication data passed down by the leader when
> spawning a worker. So, if we were to pass down the authn, we are
> going to need a new PARALLEL_KEY_* to serialize and restore the data
> passed down via a DSM like any other states as per the business in
> parallel.c. Jacob, what do you think?
I guess it depends on what we want MyProcPort to look like in a
parallel worker. Are we comfortable having most of it be blank/useless?
Does it need to be filled in?
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-03-03 19:46:00 | Re: casting operand to proper type in BlockIdGetBlockNumber |
| Previous Message | Jacob Champion | 2022-03-03 19:12:11 | Re: [PATCH] Expose port->authn_id to extensions and triggers |