pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Drouvot, Bertrand <bdrouvot@amazon.com>
To: Jacob Champion <jchampion@timescale.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: sfrost@snowman.net <sfrost@snowman.net>
Cc: rjuju123@gmail.com <rjuju123@gmail.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Cc: andres@anarazel.de <andres@anarazel.de>
Subject: Re: [PATCH] Expose port->authn_id to extensions and triggers
Date: Fri, 5 Aug 2022 12:48:33 +0200
Message-ID: <cc8aaffb-1008-eaf6-090e-2461cbe6e1cf@amazon.com> (raw)
In-Reply-To: <3b678314-054a-6119-b373-4574067f404e@timescale.com>
References: <20220329235332.z4q5hgv7jsmcavzv@alap3.anarazel.de>
	<Yk108M6LazJT7Vsj@paquier.xyz>
	<300712f85a30acecaa5c8f16c968b95537bfebd8.camel@vmware.com>
	<Yk4srPndS0tuvJso@paquier.xyz>
	<CAAWbhmhRAJpHsJS4QcjkBZCh7OrEh3sDXKhQpze5gn5_w7JCjQ@mail.gmail.com>
	<CA+TgmobAjhB5xpQ+9pP4mmaWgB53=nwXYELscVEXBByRRS40VA@mail.gmail.com>
	<CAAWbhmhxj_g-U_BRmUcWPQ0PH3tFAkQT8YChbxSW508ApcVKXw@mail.gmail.com>
	<YplYC3Tng/3WGYbv@paquier.xyz>
	<200677.1654265052@sss.pgh.pa.us>
	<CA+TgmoY22u4JUuPtA7BYs2M8o9zWJh7_dViwoqUBU7DS+_kCyA@mail.gmail.com>
	<CAAWbhmj340fKUMO-a=3BZKw4RfvWroz_V=E_9bowoxeAxFkCSQ@mail.gmail.com>
	<CA+Tgmoa2ed6X+qDKvs6NZ=h0hQ2OJjgnmoBF2LwRagE6R5qAAw@mail.gmail.com>
	<CAAWbhmhfzt+hYiTXi3f0V_E5E+E_mmzd_x+p9zjs_NvBpJ36pA@mail.gmail.com>
	<CA+TgmoZmRAkOgNzSqRxzJ=Kok_NYHZ57X2ZKRh=cfoCukp4f_Q@mail.gmail.com>
	<CAAWbhmjPu2VNS8MhwDp=+hu61EsJ3zf_rTRtyZ8Qw08eAhg_pA@mail.gmail.com>
	<f98e0b81-96cb-b0d8-c483-e99563cc44b4@amazon.com>
	<3b678314-054a-6119-b373-4574067f404e@timescale.com>

Hi,

On 8/2/22 11:57 PM, Jacob Champion wrote:
> On 6/22/22 06:31, Drouvot, Bertrand wrote:
>> FWIW, I just created a new thread to expose the port->authn_id through
>> the SYSTEM_USER sql reserved word.
> Review for both seems to have dried up a bit. I'm not particularly
> invested in my code, but I do want to see *a* solution go in. So if it
> helps the review momentum for me to withdraw this patch and put my
> effort into SYSTEM_USER, I can do that no problem.
>
> Thoughts from prior reviewers? Is SYSTEM_USER the way to go?

I did not look in detail to this thread, but if the goal is "only" to 
expose authn_id (as the subject describes) then it seems to me that 
SYSTEM_USER [1] is the way to go.

[1]: https://commitfest.postgresql.org/39/3703/

-- 
Bertrand Drouvot
Amazon Web Services: https://aws.amazon.com






view thread (89+ messages)  latest in thread

Message-ID: <cc8aaffb-1008-eaf6-090e-2461cbe6e1cf@amazon.com>
Permalink:  ../cc8aaffb-1008-eaf6-090e-2461cbe6e1cf@amazon.com/
Also on:    postgresql.org/message-id/cc8aaffb-1008-eaf6-090e-2461cbe6e1cf@amazon.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-hackers@postgresql.org
  Cc: bdrouvot@amazon.com, jchampion@timescale.com, robertmhaas@gmail.com, tgl@sss.pgh.pa.us, michael@paquier.xyz, sfrost@snowman.net, rjuju123@gmail.com, andres@anarazel.de
  Subject: Re: [PATCH] Expose port->authn_id to extensions and triggers
  In-Reply-To: <cc8aaffb-1008-eaf6-090e-2461cbe6e1cf@amazon.com>
  References: <20220329235332.z4q5hgv7jsmcavzv@alap3.anarazel.de> <300712f85a30acecaa5c8f16c968b95537bfebd8.camel@vmware.com> <Yk4srPndS0tuvJso@paquier.xyz> <CAAWbhmhRAJpHsJS4QcjkBZCh7OrEh3sDXKhQpze5gn5_w7JCjQ@mail.gmail.com> <CA+TgmobAjhB5xpQ+9pP4mmaWgB53=nwXYELscVEXBByRRS40VA@mail.gmail.com> <CAAWbhmhxj_g-U_BRmUcWPQ0PH3tFAkQT8YChbxSW508ApcVKXw@mail.gmail.com> <YplYC3Tng/3WGYbv@paquier.xyz> <200677.1654265052@sss.pgh.pa.us> <CA+TgmoY22u4JUuPtA7BYs2M8o9zWJh7_dViwoqUBU7DS+_kCyA@mail.gmail.com> <CAAWbhmj340fKUMO-a=3BZKw4RfvWroz_V=E_9bowoxeAxFkCSQ@mail.gmail.com> <CA+Tgmoa2ed6X+qDKvs6NZ=h0hQ2OJjgnmoBF2LwRagE6R5qAAw@mail.gmail.com> <CAAWbhmhfzt+hYiTXi3f0V_E5E+E_mmzd_x+p9zjs_NvBpJ36pA@mail.gmail.com> <CA+TgmoZmRAkOgNzSqRxzJ=Kok_NYHZ57X2ZKRh=cfoCukp4f_Q@mail.gmail.com> <CAAWbhmjPu2VNS8MhwDp=+hu61EsJ3zf_rTRtyZ8Qw08eAhg_pA@mail.gmail.com> <f98e0b81-96cb-b0d8-c483-e99563cc44b4@amazon.com> <3b678314-054a-6119-b373-4574067f404e@timescale.com> <cc8aaffb-1008-eaf6-090e-2461cbe6e1cf@amazon.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox