Re: Tracking role modification timestamps in pg_authid / pg_roles

Hi Andres,

On Fri, 21 Aug 2026 at 21:32, Andres Freund <andres(at)anarazel(dot)de> wrote:

> I'm not suggesting to do anything. I want to know why pg_authid, given
> Gabrielle's logic does apply just as much to many other object types. I
> would bet a fair amount of money that if we add it for authid there will be
> a lot of patches for other objects. So it seems bogus to just discuss doing
> this for one catalog in isolation.
>

Fair, and I should have drawn the line explicitly in the first mail rather
than leaving it to be inferred. Also, to Andrew's question: no, not all
catalog objects. The boundary I would propose is global objects, concretely
roles, databases and, if necessary, tablespaces.

On the expectation of a lot of follow-up patches, I think the boundary can
be based on event triggers: they already provide a way to get this
information for other object types, and they deliberately do not fire for
shared objects, which is what leaves global objects without an answer.

Happy to put together a PoC covering the three if that scope sounds
reasonable.

Thanks,
Gabriele
--
Gabriele Bartolini
VP, Chief Architect, Kubernetes
enterprisedb.com / Melbourne, Australia