Re: Standardizing how pg_waldump presents recovery conflict XID cutoffs
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Peter Geoghegan <pg@bowt.ie>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-11-15T20:29:37Z
Lists: pgsql-hackers
Hi, I like the idea of this, but: On 2022-11-15 10:24:05 -0800, Peter Geoghegan wrote: > I'm not necessarily that attached to the name latestCommittedXid. It > is more accurate, but it's also a little bit too similar to another > common XID symbol name, latestCompletedXid. Can anyone suggest an > alternative? ... I strongly dislike latestCommittedXid. That seems at least as misleading as latestRemovedXid and has the danger of confusion with latestCompletedXid as you mention. How about latestAffectedXid? Based on a quick scroll through the changed structures it seems like it'd be reasonably discriptive for most? Greetings, Andres Freund
Commits
-
Standardize rmgrdesc recovery conflict XID output.
- 1489b1ce7282 16.0 landed
-
Avoid hot standby cancels from VAC FREEZE
- 66fbcb0d2e1b 9.5.0 cited