Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts - Mailing list pgsql-bugs

From Tom Lane
Subject Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts
Date
Msg-id 6333.1405962201@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-bugs
Andres Freund <andres@2ndquadrant.com> writes:
> On 2014-07-21 12:43:24 -0400, Tom Lane wrote:
>> Will fix.

> I wonder if GetTopTransactionId()/MultiXactIdSetOldestMember() and using
> lastSane* = ReadNew* isn't sufficient. After the xid assignment
> concurrent GetOldest* can't go below the ReadNew* values anymore, right?

I don't see any point in being picky about it.  What we want is to reject
values that are conclusively bogus; things that are just close to bogus
are not so interesting.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts
Next
From: Andres Freund
Date:
Subject: Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts