Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nX9y1-0007Zn-J4 for pgsql-hackers@arkaria.postgresql.org; Wed, 23 Mar 2022 23:00:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nX9y0-0002XF-EO for pgsql-hackers@arkaria.postgresql.org; Wed, 23 Mar 2022 23:00:36 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nX9y0-0002Wz-50 for pgsql-hackers@lists.postgresql.org; Wed, 23 Mar 2022 23:00:36 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nX9xx-0007mO-Pv for pgsql-hackers@postgresql.org; Wed, 23 Mar 2022 23:00:35 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 22NN0S0t2886825; Wed, 23 Mar 2022 19:00:28 -0400 From: Tom Lane To: Jacob Champion cc: "sfrost@snowman.net" , "rjuju123@gmail.com" , "pgsql-hackers@postgresql.org" , "michael@paquier.xyz" , "andres@anarazel.de" Subject: Re: [PATCH] Expose port->authn_id to extensions and triggers In-reply-to: <60ce6b04f2e4049d04700730f1c439e325731dc4.camel@vmware.com> References: <20220225212349.gf76klktl4dmm5ah@alap3.anarazel.de> <0cead4e58257beebb96f162507151271ff2f7b54.camel@vmware.com> <20220228210036.GN10577@tamriel.snowman.net> <20220301133527.GS10577@tamriel.snowman.net> <20220302212740.krbycl3nzvp5y2k5@alap3.anarazel.de> <973625.1647556418@sss.pgh.pa.us> <60ce6b04f2e4049d04700730f1c439e325731dc4.camel@vmware.com> Comments: In-reply-to Jacob Champion message dated "Wed, 23 Mar 2022 22:52:22 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2886823.1648076428.1@sss.pgh.pa.us> Date: Wed, 23 Mar 2022 19:00:28 -0400 Message-ID: <2886824.1648076428@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Jacob Champion 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