diff options
| author | Noah Misch <noah@leadboat.com> | 2020-08-01 15:31:01 -0700 |
|---|---|---|
| committer | Noah Misch <noah@leadboat.com> | 2020-08-01 15:31:01 -0700 |
| commit | cd5e82256de5895595cdd99ecb03aea15b346f71 (patch) | |
| tree | 747def403ed87cd47308b611a7cb99eccab6db8d /src/backend/commands/explain.c | |
| parent | 9f9682783bea74bf8d93cac4f7dd65fa677f5dc7 (diff) | |
| download | postgresql-cd5e82256de5895595cdd99ecb03aea15b346f71.tar.gz postgresql-cd5e82256de5895595cdd99ecb03aea15b346f71.zip | |
Change XID and mxact limits to warn at 40M and stop at 3M.
We have edge-case bugs when assigning values in the last few dozen pages
before the wrap limit. We may introduce similar bugs in the future. At
default BLCKSZ, this makes such bugs unreachable outside of single-user
mode. Also, when VACUUM began to consume mxacts, multiStopLimit did not
change to compensate.
pg_upgrade may fail on a cluster that was already printing "must be
vacuumed" warnings. Follow the warning's instructions to clear the
warning, then run pg_upgrade again. One can still, peacefully consume
98% of XIDs or mxacts, so DBAs need not change routine VACUUM settings.
Discussion: https://postgr.es/m/20200621083513.GA3074645@rfd.leadboat.com
Diffstat (limited to 'src/backend/commands/explain.c')
0 files changed, 0 insertions, 0 deletions