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

From Robert Haas
Subject Re: [PATCH] Expose port->authn_id to extensions and triggers
Date
Msg-id CA+TgmoZmRAkOgNzSqRxzJ=Kok_NYHZ57X2ZKRh=cfoCukp4f_Q@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Expose port->authn_id to extensions and triggers  (Jacob Champion <jchampion@timescale.com>)
Responses Re: [PATCH] Expose port->authn_id to extensions and triggers
List pgsql-hackers
On Wed, Jun 8, 2022 at 7:53 PM Jacob Champion <jchampion@timescale.com> wrote:
> But I don't have any better ideas for how to achieve both. I'm fine
> with your suggestion of ClientConnectionInfo, if that sounds good to
> others; the doc comment can clarify why it differs from Port? Or add
> one of the Shared-/Gang-/Group- prefixes to it, maybe?

I don't like the prefixes, so I'd prefer explaining it in the struct comment.

-- 
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Etsuro Fujita
Date:
Subject: Re: Error from the foreign RDBMS on a foreign table I have no privilege on
Next
From: Peter Eisentraut
Date:
Subject: Re: