pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jacob Champion <pchampion@vmware.com>
To: michael@paquier.xyz <michael@paquier.xyz>
To: andres@anarazel.de <andres@anarazel.de>
Cc: rjuju123@gmail.com <rjuju123@gmail.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Cc: sfrost@snowman.net <sfrost@snowman.net>
Subject: Re: [PATCH] Expose port->authn_id to extensions and triggers
Date: Thu, 3 Mar 2022 19:16:17 +0000
Message-ID: <a521eb40f5068d902c821368f2be0c474a3c2aa6.camel@vmware.com> (raw)
In-Reply-To: <YiByHbZslaZXkcqY@paquier.xyz>
References: <a4d9baa0717ca924331cb1dd062788bd73bd14a4.camel@vmware.com>
	<d15d02c92a3e4bdb7cc7b96b0abfe97f213e4445.camel@vmware.com>
	<cdbcf8653e56340f73438e647ea5a26f021627ed.camel@vmware.com>
	<20220225212349.gf76klktl4dmm5ah@alap3.anarazel.de>
	<Yhm9BUjrCItExUJu@paquier.xyz>
	<0cead4e58257beebb96f162507151271ff2f7b54.camel@vmware.com>
	<20220228210036.GN10577@tamriel.snowman.net>
	<Yh3Czv8xFdUzFFfZ@paquier.xyz>
	<20220301133527.GS10577@tamriel.snowman.net>
	<20220302212740.krbycl3nzvp5y2k5@alap3.anarazel.de>
	<YiByHbZslaZXkcqY@paquier.xyz>

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


view thread (89+ messages)  latest in thread

Message-ID: <a521eb40f5068d902c821368f2be0c474a3c2aa6.camel@vmware.com>
Permalink:  ../a521eb40f5068d902c821368f2be0c474a3c2aa6.camel@vmware.com/
Also on:    postgresql.org/message-id/a521eb40f5068d902c821368f2be0c474a3c2aa6.camel@vmware.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-hackers@postgresql.org
  Cc: pchampion@vmware.com, michael@paquier.xyz, andres@anarazel.de, rjuju123@gmail.com, sfrost@snowman.net
  Subject: Re: [PATCH] Expose port->authn_id to extensions and triggers
  In-Reply-To: <a521eb40f5068d902c821368f2be0c474a3c2aa6.camel@vmware.com>
  References: <a4d9baa0717ca924331cb1dd062788bd73bd14a4.camel@vmware.com> <d15d02c92a3e4bdb7cc7b96b0abfe97f213e4445.camel@vmware.com> <cdbcf8653e56340f73438e647ea5a26f021627ed.camel@vmware.com> <20220225212349.gf76klktl4dmm5ah@alap3.anarazel.de> <Yhm9BUjrCItExUJu@paquier.xyz> <0cead4e58257beebb96f162507151271ff2f7b54.camel@vmware.com> <20220228210036.GN10577@tamriel.snowman.net> <Yh3Czv8xFdUzFFfZ@paquier.xyz> <20220301133527.GS10577@tamriel.snowman.net> <20220302212740.krbycl3nzvp5y2k5@alap3.anarazel.de> <YiByHbZslaZXkcqY@paquier.xyz> <a521eb40f5068d902c821368f2be0c474a3c2aa6.camel@vmware.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox