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-08-09 03:16:36
Message-ID: 6jcC9noDOoGQYmND0JDdtry2KFucKA2FMtTj6EZI8Ge6nOpR-gc8yf9hIa1G9P1RcNyz5xud7IwN4duDn2XZrlC6q0oUnt1DtIzwroNBnbU=@scottray.io
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tuesday, August 4th, 2026 at 2:42 AM, solai v <solai(dot)cdac(at)gmail(dot)com> wrote:

> The updated patch looks good to me.

Thanks for the review and testing.

Attached is v4. It changes documentation and comments only, so the
code is identical to the v3 you tested. The leave-one-out recipe
was too long and didn't handle database scoping properly, so I
removed it. Also, I rewrote and trimmed some comments and
documented two caveats, one about cross-row consistency and the
other about aggregate slot xmin contribution. Patch v4 applies to
master b5978350222.

--
Scott Ray

Attachment Content-Type Size
v4-0001-Add-pg_xmin_horizon-view-showing-per-input-horizo.patch application/octet-stream 50.5 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bryan Green 2026-08-09 03:26:40 [PATCH] Fix SIGSEGV in GrantLockLocal when OOM leaves LOCALLOCK.lockOwners NULL
Previous Message Bryan Green 2026-08-09 02:59:57 [PATCH] Avoid uninitialized-value error in poll_query_until timeout diagnostic