Skip site navigation (1) Skip section navigation (2)

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: (view raw, whole thread or download thread mbox)
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      
PostgreSQL Development, 24x7 Support, Training & Services

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

In response to


pgsql-hackers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group