Re: MultiXact truncation, startup et al.

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: MultiXact truncation, startup et al.
Date: 2013-11-29 19:30:08
Message-ID: 20131129193008.GP5513@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

New versions of all these patches, plus one more patch which removes the
behavior that HeapTupleGetUpdateXid checks for aborted updates. (Turns
out this was necessary to get freezing right.) My previous patch to
avoid InvalidXid as page prune point is reverted in there, too (no
longer necessary.)

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

Attachment Content-Type Size
0001-Replace-hardcoded-200000000-with-autovacuum_freeze_m.patch text/x-diff 2.1 KB
0002-Fix-full-table-vacuum-request-mechanism-for-MultiXac.patch text/x-diff 10.0 KB
0003-Truncate-pg_multixact-s-contents-during-crash-recove.patch text/x-diff 8.1 KB
0004-Don-t-TransactionIdDidAbort-in-HeapTupleGetUpdateXid.patch text/x-diff 10.9 KB
0005-Fix-a-couple-of-bugs-in-MultiXactId-freezing.patch text/x-diff 9.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2013-11-29 19:39:55 Re: [RFC] overflow checks optimized away
Previous Message Heikki Linnakangas 2013-11-29 19:17:08 Re: GIN improvements part 1: additional information