| From: | "Drouvot, Bertrand" <bdrouvot(at)amazon(dot)com> |
|---|---|
| To: | Jacob Champion <jchampion(at)timescale(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>, "sfrost(at)snowman(dot)net" <sfrost(at)snowman(dot)net>, "rjuju123(at)gmail(dot)com" <rjuju123(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "andres(at)anarazel(dot)de" <andres(at)anarazel(dot)de> |
| Subject: | Re: [PATCH] Expose port->authn_id to extensions and triggers |
| Date: | 2022-06-22 13:31:16 |
| Message-ID: | f98e0b81-96cb-b0d8-c483-e99563cc44b4@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 can confirm the sender and know the content is safe.
>
>
>
> On Thu, Jun 9, 2022 at 6:23 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> On Wed, Jun 8, 2022 at 7:53 PM Jacob Champion <jchampion(at)timescale(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-06-22 13:45:20 | Re: Unify DLSUFFIX on Darwin |
| Previous Message | Peter Eisentraut | 2022-06-22 13:29:24 | Re: CREATE TABLE ( .. STORAGE ..) |