Re: pg_xmin_horizon: a system view of everything pinning the xmin horizon

From: Scott Ray <scott(at)scottray(dot)io>
To: solai v <solai(dot)cdac(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_xmin_horizon: a system view of everything pinning the xmin horizon
Date: 2026-07-18 07:14:26
Message-ID: _9LLi6qXTdunP1OYGi4li3De6B96wFahhKvCsUSWH_iiap4W-vC40Vcp3ib6HPnzW8QAW58Es8RfOcZEttTbqfUcEJ_lj_4GBoss-a5bHzk=@scottray.io
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thursday, July 16th, 2026 at 11:56 PM, solai v <solai(dot)cdac(at)gmail(dot)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 Content-Type Size
v2-0001-Add-pg_xmin_horizon-view-showing-per-input-horizo.patch application/octet-stream 54.6 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message 김선동 2026-07-18 07:30:51 Re: [PATCH v1] amcheck: Allow interrupting the child-level rightlink walk
Previous Message Amit Kapila 2026-07-18 06:40:10 Re: REASSIGN OWNED vs. relisshared dep on !relisshared