On Fri, Dec 15, 2023 at 9:53 AM Thomas Munro wrote:
> ... We've seen a system with ~30GB of files in there
> (note: full/untruncated be would be 2³² xids × sizeof(uint64_t) =
> 32GB). It's not just a gradual disk space leak: according to disk
> space monitoring, this system suddenly wrote ~half o
Hi,
Our pg_serial truncation logic is a bit broken, as described by the
comments in CheckPointPredicate() (a sort of race between xid cycles
and checkpointing). We've seen a system with ~30GB of files in there
(note: full/untruncated be would be 2³² xids × sizeof(uint64_t) =
32GB). It's not just
