Re: [PATCH] Expose port->authn_id to extensions and triggers - Mailing list pgsql-hackers

From Andy Fan
Subject Re: [PATCH] Expose port->authn_id to extensions and triggers
Date
Msg-id 875xyqhzs6.fsf@163.com
Whole thread Raw
In response to Re: [PATCH] Expose port->authn_id to extensions and triggers  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Hi,

Michael Paquier <michael@paquier.xyz> writes:

> [[PGP Signed Part:Undecided]]
> On Tue, Aug 23, 2022 at 10:04:30AM -0700, Jacob Champion wrote:
>
> My main worry here is EXEC_BACKEND, where we would just use our own
> implementation of fork(), and it is a bad idea at the end to leave
> that untouched while we could have code paths that attempt to access
> it.  At the end, I have moved the initialization at the same place as
> where we set MyProcPort for a backend in BackendInitialize(), mainly
> as a matter of consistency because ClientConnectionInfo is aimed at
> being a subset of that.  And applied.

I found a compiler complaint of this patch. The attached fix that.

-- 
Best Regards
Andy Fan


Attachment

pgsql-hackers by date:

Previous
From: Andy Fan
Date:
Subject: Re: make add_paths_to_append_rel aware of startup cost
Next
From: jian he
Date:
Subject: Re: Make COPY format extendable: Extract COPY TO format implementations