Re: Raising stop and warn limits - Mailing list pgsql-hackers

From Noah Misch
Subject Re: Raising stop and warn limits
Date
Msg-id 20200628062004.GA3366199@rfd.leadboat.com
Whole thread Raw
In response to Raising stop and warn limits  (Noah Misch <noah@leadboat.com>)
List pgsql-hackers
On Sun, Jun 21, 2020 at 01:35:13AM -0700, Noah Misch wrote:
> In brief, I'm proposing to raise xidWrapLimit-xidStopLimit to 3M and
> xidWrapLimit-xidWarnLimit to 40M.  Likewise for mxact counterparts.

Here's the patch for it.

> 1. VACUUM, to advance a limit, may assign IDs subject to one of the limits.
>    VACUUM formerly consumed XIDs, not mxacts.  It now consumes mxacts, not
>    XIDs.

Correction: a lazy_truncate_heap() at wal_level!=minimal does assign an XID,
so XID consumption is impossible with "VACUUM (TRUNCATE false)" but possible
otherwise.  "VACUUM (ANALYZE)", which a DBA might do by reflex, also assigns
XIDs.  (These corrections do not affect $SUBJECT.)

Attachment

pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: update substring pattern matching syntax
Next
From: Peter Eisentraut
Date:
Subject: Re: Fwd: PostgreSQL: WolfSSL support