Re: [PATCH] Expose port->authn_id to extensions and triggers

From: Jacob Champion <pchampion(at)vmware(dot)com>
To: "tgl(at)sss(dot)pgh(dot)pa(dot)us" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "andres(at)anarazel(dot)de" <andres(at)anarazel(dot)de>, "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>, "michael(at)paquier(dot)xyz" <michael(at)paquier(dot)xyz>
Subject: Re: [PATCH] Expose port->authn_id to extensions and triggers
Date: 2022-03-23 23:06:14
Message-ID: 8a480a78f24a10a83f58e1ce5d462b0a93412a99.camel@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 2022-03-23 at 19:00 -0400, Tom Lane wrote:
> Hm. I was more envisioning getting the "sharable" info out of Port
> entirely, although I'm not quite sure where it should go instead.

If it helps, I can move the substruct out and up to a new global struct
(MyProcShared?). At this point I think it's mostly search-and-replace.

--Jacob

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2022-03-23 23:07:01 Re: multithreaded zstd backup compression for client and server
Previous Message Tom Lane 2022-03-23 23:02:30 Re: ubsan