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 _9LLi6qXTdunP1OYGi4li3De6B96wFahhKvCsUSWH_iiap4W-vC40Vcp3ib6HPnzW8QAW58Es8RfOcZEttTbqfUcEJ_lj_4GBoss-a5bHzk=@scottray.io
Whole thread
List pgsql-hackers
On Thursday, July 16th, 2026 at 11:56 PM, solai v <solai.cdac@gmail.com> wrote:

> I would like to suggest that it may also be worth considering exposing
> the database name (datname) in addition to datid for better
> observability and easier interpretation by DBAs as a future
> enhancement, although the current implementation is functionally
> correct.

Thanks for testing the patch.

Adding datname is a good idea and follows the precedent of
pg_stat_activity, pg_replication_slots, and pg_prepared_xacts. The
attached v2 adds datname.

--
Scott Ray
Attachment

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: REASSIGN OWNED vs. relisshared dep on !relisshared
Next
From: 김선동
Date:
Subject: Re: [PATCH v1] amcheck: Allow interrupting the child-level rightlink walk