Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts
Date: 2014-07-20 23:04:30
Message-ID: 18673.1405897470@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> If any *single* full table vacuum after that calls
> vac_update_datfrozenxid() which just needs its datfrozenxid advance by
> one we're in trouble: vac_truncate_clog() will be called with minMulti =
> GetOldestMultiXactId().

Uh, no, the cutoff is GetOldestMultiXactId minus
vacuum_multixact_freeze_min_age (or the autovac equivalent).
See vacuum_set_xid_limits.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2014-07-20 23:11:40 Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts
Previous Message Andres Freund 2014-07-20 22:56:53 Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts