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-21 17:03:21
Message-ID: 6333.1405962201@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:
> 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2014-07-21 17:09:53 Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts
Previous Message Andres Freund 2014-07-21 16:48:57 Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts