Re: [PATCH] Clarify the behavior of the system when approaching XID wraparound

John Naylor <john.naylor@enterprisedb.com>

From: John Naylor <john.naylor@enterprisedb.com>

To: Peter Geoghegan <pg@bowt.ie>

Cc: Aleksander Alekseev <aleksander@timescale.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Pavel Borisov <pashkin.elfe@gmail.com>

Date: 2023-05-13T04:13:50Z

Lists: pgsql-hackers

Attachments

v9-0003-Rough-draft-of-complete-steps-to-recover-from-M-X.patch (text/x-patch) patch v9-0003
v9-0001-Correct-outdated-docs-and-messages-regarding-XID-.patch (text/x-patch) patch v9-0001
v9-0002-Stop-telling-users-to-run-VACUUM-in-a-single-user.patch (text/x-patch) patch v9-0002

Attached is v9, which is mostly editing the steps for restoring normal
operation, which are in 0003 now but will be squashed into 0002. Comments
to polish the wording welcome.

-- 
John Naylor
EDB: http://www.enterprisedb.com

Commits

Reword messages about impending (M)XID exhaustion.
- 2406c4e34ccc 17.0 landed
Talk about assigning, rather than generating, new MultiXactIds.
- a1a5da8cb74b 17.0 landed
Update the documentation on recovering from (M)XID exhaustion.
- 81b3df0f1b89 14.10 landed
- fdfb141a7467 15.5 landed
- 08c1795c52b8 16.1 landed
- a70bce43fbce 17.0 landed