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

From Tom Lane
Subject Re: [PATCH] Expose port->authn_id to extensions and triggers
Date
Msg-id 200677.1654265052@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH] Expose port->authn_id to extensions and triggers  (Michael Paquier <michael@paquier.xyz>)
Responses Re: [PATCH] Expose port->authn_id to extensions and triggers  (Michael Paquier <michael@paquier.xyz>)
Re: [PATCH] Expose port->authn_id to extensions and triggers  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes:
> ParallelPortInfo sounds kind of right for the job to me in this set of
> proposals, as the data is from the Port, and that's some information
> shared between all the parallel workers and the leader.

I agree with Robert's complaint that Parallel is far too generic
a term here.  Also, the fact that this data is currently in struct
Port seems like an artifact.

Don't we have a term for the set of processes comprising a leader
plus parallel workers?  If we called that set FooGroup, then
something like FooGroupSharedInfo would be on-point.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: [v15 beta] pg_upgrade failed if earlier executed with -c switch
Next
From: Nathan Bossart
Date:
Subject: Re: Proposal: adding a better description in psql command about large objects