Re: MultiXactId error after upgrade to 9.3.4

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, "pgsql-hackers\(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: MultiXactId error after upgrade to 9.3.4
Date: 2016-06-17 13:33:02
Message-ID: 87a8ikq6zk.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>>>> "Robert" == Robert Haas <robertmhaas(at)gmail(dot)com> writes:

>> Why is the correct rule not "check for and ignore pre-upgrade mxids
>> before even trying to fetch members"?

Robert> I entirely believe that's the correct rule, but doesn't
Robert> implementing it require a crystal balll?

Why would it? Pre-9.3 mxids are identified by the combination of flag
bits in the infomask, see Alvaro's patch.

--
Andrew (irc:RhodiumToad)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-06-17 14:01:12 Re: Restriction of windows functions
Previous Message Robert Haas 2016-06-17 13:29:05 Re: ERROR: ORDER/GROUP BY expression not found in targetlist