Re: Incomplete freezing when truncating a relation during vacuum

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Noah Misch <noah(at)leadboat(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Incomplete freezing when truncating a relation during vacuum
Date: 2013-12-01 20:27:44
Message-ID: 4751.1385929664@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> The VACUUM implementation in 9.3 had several bugs: It removed multixact
> xmax values without regard of the importance of contained xids, it did
> not remove multixacts if the contained xids were too old and it relied
> on hint bits when checking whether a row needed to be frozen which might
> not have been set on replicas.

Uh ... what does the last have to do with it? Surely we don't run
VACUUM on replicas. Or are you talking about what might happen when
VACUUM is run on a former replica that's been promoted to master?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2013-12-01 20:38:18 Re: Incomplete freezing when truncating a relation during vacuum
Previous Message Noah Misch 2013-12-01 19:39:28 Re: Incomplete freezing when truncating a relation during vacuum