Re: ERROR: cannot GetMultiXactIdMembers() during recovery

From: Andres Freund <andres(at)anarazel(dot)de>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marko Tiikkaja <marko(at)joh(dot)to>, Andres Freund <andres(at)2ndquadrant(dot)com>, hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ERROR: cannot GetMultiXactIdMembers() during recovery
Date: 2015-05-18 17:21:47
Message-ID: 20150518172147.GX9584@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2015-05-18 14:13:51 -0300, Alvaro Herrera wrote:
> Hmm, AFAICS the problematic check was introduced by this commit:
>
> commit 9f1e051adefb2f29e757cf426b03db20d3f8a26d
> Author: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
> Date: Fri Nov 29 11:26:41 2013 -0300
>
> so it isn't hot off the oven, but it is a regression.

Hasn't that just changed the symptoms? I don't recall exactly, but my
recollection is that the multixact code isn't ready at that point and
hasn't initialized a bunch of important variables yet. Leading to errors
in the SLRU etc.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-05-18 17:28:33 Re: How does MSVC's fetchRegressOpts() work at all?
Previous Message Peter Geoghegan 2015-05-18 17:18:26 Re: jsonb concatenate operator's semantics seem questionable