Re: Standardizing how pg_waldump presents recovery conflict XID cutoffs

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Standardizing how pg_waldump presents recovery conflict XID cutoffs
Date: 2022-11-16 22:14:30
Message-ID: CAH2-Wzn0uQGMPd5u9pMZkvFbXS9V0knvLYqVq0Jnge-d_QEOiQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 15, 2022 at 8:48 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> Okay, let's go with snapshotConflictHorizon. I'll use that name in the
> next revision, which I should be able to post tomorrow.

Attached is a somewhat cleaned up version that uses that symbol name
for everything.

--
Peter Geoghegan

Attachment Content-Type Size
v2-0001-Standardize-rmgrdesc-recovery-conflict-XID-output.patch application/octet-stream 47.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-11-16 22:26:03 Re: Allow single table VACUUM in transaction block
Previous Message Greg Stark 2022-11-16 22:14:07 Re: Allow single table VACUUM in transaction block