Re: PostgreSQL 17: protecting role attributes between verification and COMMIT

From: Olivier Gautherot <ogautherot(at)gautherot(dot)net>
To: Dustin Sanza <dustin(dot)sanza(at)gmail(dot)com>
Cc: PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: PostgreSQL 17: protecting role attributes between verification and COMMIT
Date: 2026-10-24 07:27:10
Message-ID: CAJ7S9TWBAdQupakPzH438SSyEm7Q7upzCjL4i3Ypue-VW3KFuQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi Dustin,

El sáb, 24 de oct de 2026, 8:45 a.m., Dustin Sanza <dustin(dot)sanza(at)gmail(dot)com>
escribió:

> Hi,
>
> I'm looking for a supported PostgreSQL 17 mechanism to keep selected
> role attributes and memberships stable between verification and
> COMMIT. This is a design question, not a bug report.
>
> Assume the transaction's role is NOSUPERUSER, has CREATEROLE and ADMIN
> OPTION on the relevant non-superuser roles, but has no direct UPDATE
> privilege on system catalogs. Other legitimately authorized
> administrative sessions may be running; this is not an attempt to
> constrain a malicious superuser.
>
> <...>

> The narrow question: under the privileges above, is there supported
> SQL that prevents or safely serializes concurrent ALTER ROLE attribute
> changes until COMMIT without first rewriting those attributes and
> potentially concealing unexpected drift?
>

As I understand it, you may alter roles between transactions for that user,
not during a transaction.

<...>
> Please keep me copied on replies, as I am not subscribed.
>
> Thank you,
> Dustin Sanza
>

Best regards
Olivier

>
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message sutyak 2026-10-24 14:50:36 PG18.6 Windows Initialization
Previous Message Dustin Sanza 2026-10-23 21:20:17 PostgreSQL 17: protecting role attributes between verification and COMMIT