pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jacob Champion <pchampion@vmware.com>
Cc: sfrost@snowman.net <sfrost@snowman.net>
Cc: rjuju123@gmail.com <rjuju123@gmail.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Cc: michael@paquier.xyz <michael@paquier.xyz>
Cc: andres@anarazel.de <andres@anarazel.de>
Subject: Re: [PATCH] Expose port->authn_id to extensions and triggers
Date: Wed, 23 Mar 2022 19:00:28 -0400
Message-ID: <2886824.1648076428@sss.pgh.pa.us> (raw)
In-Reply-To: <60ce6b04f2e4049d04700730f1c439e325731dc4.camel@vmware.com>
References: <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>
	<YiFvNIm4mvvqDo54@paquier.xyz>
	<c6ffdec0f5da8e149237509fc64e1c41fc8da668.camel@vmware.com>
	<973625.1647556418@sss.pgh.pa.us>
	<60ce6b04f2e4049d04700730f1c439e325731dc4.camel@vmware.com>

Jacob Champion <pchampion@vmware.com> writes:
> On Thu, 2022-03-17 at 18:33 -0400, Tom Lane wrote:
>> I think what we ought to do here is separate out the data that we think
>> parallel workers need access to.  It does not seem wise to say "workers
>> can access fields A,B,C of MyPort but not fields X,Y,Z".  I do not have
>> a concrete proposal for fixing it though.

> v6-0002 has my first attempt at this. I moved authn_id into its own
> substruct inside Port, which gets serialized with the parallel key
> machinery. (My name selection of "SharedPort" is pretty bland.)

Hm.  I was more envisioning getting the "sharable" info out of Port
entirely, although I'm not quite sure where it should go instead.

			regards, tom lane





view thread (89+ messages)  latest in thread

Message-ID: <2886824.1648076428@sss.pgh.pa.us>
Permalink:  ../2886824.1648076428@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2886824.1648076428@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, pchampion@vmware.com, sfrost@snowman.net, rjuju123@gmail.com, michael@paquier.xyz, andres@anarazel.de
  Subject: Re: [PATCH] Expose port->authn_id to extensions and triggers
  In-Reply-To: <2886824.1648076428@sss.pgh.pa.us>
  References: <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> <YiFvNIm4mvvqDo54@paquier.xyz> <c6ffdec0f5da8e149237509fc64e1c41fc8da668.camel@vmware.com> <973625.1647556418@sss.pgh.pa.us> <60ce6b04f2e4049d04700730f1c439e325731dc4.camel@vmware.com> <2886824.1648076428@sss.pgh.pa.us>

* 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