Re: pg_xmin_horizon: a system view of everything pinning the xmin horizon - Mailing list pgsql-hackers

From Scott Ray
Subject Re: pg_xmin_horizon: a system view of everything pinning the xmin horizon
Date
Msg-id 4U4e3pJ5KQ-tMTpmBNHbrWptLVZb2m3DJoryggEAnGJKGhrcYoiDzE-ZvuTpUBHiX5EREnX1Ni-aqolFYkwCQaJnEBCfik589NXNcaOnhdc=@scottray.io
Whole thread
In response to Re: pg_xmin_horizon: a system view of everything pinning the xmin horizon  (surya poondla <suryapoondla4@gmail.com>)
List pgsql-hackers
Hi Surya,

On Thursday, September 17th, 2026 at 1:14 PM, surya poondla <suryapoondla4@gmail.com> wrote:

> Bharath pointed out one asymmetry already i.e pg_stat_activity shows
> pid, datid, xid and xmin to unprivileged non-owners while
> pg_xmin_horizon shows nothing, and this would be one in the other
> direction if the ACL were ever loosened or EXECUTE granted directly.
> Would it be worth applying HAS_PGSTAT_PERMISSIONS per row in the SRF?

No view in PG mixes revoke from PUBLIC with permissions checks per row.
pg_shmem_allocations, pg_backend_memory_contexts,
pg_dsm_registry_allocations, and pg_aios all use the former only.  This
patch follows that convention, sets a conservative default, and trusts
DBAs to configure access.

--
Scott Ray
Attachment

pgsql-hackers by date:

Previous
From: Manu
Date:
Subject: Re: BUG #19686: Rolling back SET TABLESPACE
Next
From: Cagri Biroglu
Date:
Subject: Re: Per-table resync for logical replication subscriptions