| From: | Fujii Masao <fujii(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Remove replication slot advice from MultiXact wraparound hints |
| Date: | 2026-07-03 02:23:55 |
| Message-ID: | E1wfTZL-0017sA-23@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Remove replication slot advice from MultiXact wraparound hints
Previously, MultiXactId wraparound hints suggested dropping stale
replication slots. While that advice is appropriate for transaction ID
wraparound, where replication slots can hold back XID horizons,
it was misleading for MultiXactId wraparound. Following it could lead
users to drop replication slots unnecessarily without helping resolve
the MultiXactId wraparound condition.
MultiXact cleanup is not directly delayed by replication slots.
Instead, it depends on whether old MultiXactIds can still be seen
as live by running transactions.
This commit removes the replication slot advice from MultiXactId
wraparound hints, and documents that stale replication slots are
normally not relevant to resolving MultiXactId wraparound problems.
Backpatch to all supported branches.
BUG #18876
Reported-by: Haruka Takatsuka <harukat(at)sraoss(dot)co(dot)jp>
Author: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Discussion: https://postgr.es/m/18876-0d0b53bad5a1f4c1@postgresql.org
Backpatch-through: 14
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/084734ff5a4249f0095771ee1addedbd41a88a18
Modified Files
--------------
doc/src/sgml/maintenance.sgml | 6 ++++++
src/backend/access/transam/multixact.c | 12 ++++++------
src/backend/commands/vacuum.c | 2 +-
3 files changed, 13 insertions(+), 7 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2026-07-03 02:24:09 | pgsql: Remove replication slot advice from MultiXact wraparound hints |
| Previous Message | Fujii Masao | 2026-07-02 23:49:05 | pgsql: Add log_statement_max_length GUC to limit logged statement text |