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

Hi,

On 6/10/22 7:58 PM, Jacob Champion wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you
canconfirm the sender and know the content is safe.
 
>
>
>
> On Thu, Jun 9, 2022 at 6:23 AM Robert Haas <robertmhaas@gmail.com> wrote:
>> 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.
> Done that way in v11.
>
> Thanks!
> --Jacob

FWIW, I just created a new thread to expose the port->authn_id through 
the SYSTEM_USER sql reserved word.

Regards,

Bertrand