Menu

1 / 6

PostgreSQL 19 removes the MultiXact members wall. Reclamation still waits for template0.

DEV Community: database·Firat Celik·about 14 hours ago
#GS1dq8oh
#devtodatabase#devto#dev#members#multixact
Long article (4880 words) — no AI summary yet.
Reading 0:00
15s threshold

Between May 10 and May 17, 2025, Metronome had four outages that each lasted over an hour. Their dashboards showed "less than 50% utilization" of the configured MultiXact ID threshold ( autovacuum_multixact_freeze_max_age = 400 million) on an Aurora PostgreSQL 13.18 cluster of more than 30 TB. The limit they actually hit was MultiXact member space . In their words, "PostgreSQL does not expose metrics for member space consumption". ( Metronome RCA )

Member space is addressed by a 32-bit offset in every release through 18. PostgreSQL 19 widens it to 64 bits ( commit bd8d9c9bd : "This eliminates MultiXactOffset wraparound and the 2^32 limit on the total number of multixid members. Multixids are still limited to 2^31").

I rebuilt the failure from scratch on PostgreSQL 18.7 and on 19.0, released on 19 November 2026, with 19 RC2 as a cross-check. 19.0 reproduced every RC2 count I reran exactly. Short version:

The member-offset stop is gone in 19; the 2^31 MultiXact ID stop is not.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.