| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Gabriele Bartolini <gabriele(dot)bartolini(at)enterprisedb(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Tracking role modification timestamps in pg_authid / pg_roles |
| Date: | 2026-08-21 04:40:56 |
| Message-ID: | 5qh7ejjkh3526tpcjosqulitnvgumj25wsxv7iqjgev3qqoi7g@w73fcwn2ul5l |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2026-08-21 13:07:42 +1000, Gabriele Bartolini wrote:
> I'd like to propose adding a small column to pg_authid (rollastupdated
> timestamptz), that records when a role was last created or altered, and get
> feedback on the idea before polishing it for a commitfest (a working
> prototype is attached).
>
> Why?
> Tools that manage PostgreSQL roles declaratively all reconcile in the same
> way: given a desired set of roles and attributes, make the live cluster
> match it, repeatedly and idempotently.
My question is why this is needed for pg_authid and not any of the other
catalogs? Adding one-off code for different catalogs one-by-one would ... not
be likely to result in good code.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2026-08-21 04:41:14 | Re: Thread-safe stringToNode() / pg_strtok() |
| Previous Message | Peter Smith | 2026-08-21 04:30:40 | Re: Support EXCEPT for TABLES IN SCHEMA publications |