From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com> |
Cc: | Michał Kłeczek <michal(at)kleczek(dot)org>, Eric Hanson <eric(at)aquameta(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SET ROLE x NO RESET |
Date: | 2024-01-02 17:36:38 |
Message-ID: | CA+TgmoYtfNC+ZqthO0naskxG+WnN71=0xQGcC++Y+Y8Czadktg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Dec 31, 2023 at 2:20 PM Joe Conway <mail(at)joeconway(dot)com> wrote:
> On 12/30/23 17:19, Michał Kłeczek wrote:
> >> On 30 Dec 2023, at 17:16, Eric Hanson <eric(at)aquameta(dot)com> wrote:
> >>
> >> What do you think of adding a NO RESET option to the SET ROLE command?
> >
> > What I proposed some time ago is SET ROLE … GUARDED BY ‘password’, so
> > that you could later: RESET ROLE WITH ‘password'
>
> I like that too, but see it as a separate feature. FWIW that is also
> supported by the set_user extension referenced elsewhere on this thread.
IMHO, the best solution here would be a protocol message to change the
session user. The pooler could use that repeatedly on the same
session, but refuse to propagate such messages from client
connections.
--
Robert Haas
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2024-01-02 17:43:01 | Re: Build versionless .so for Android |
Previous Message | Melanie Plageman | 2024-01-02 17:36:18 | Re: Confine vacuum skip logic to lazy_scan_skip |