Date: Mon, 18 May 2015 14:36:23 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Andres Freund <andres@anarazel.de>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Marko Tiikkaja <marko@joh.to>,
 Andres Freund <andres@2ndquadrant.com>,
 hackers <pgsql-hackers@postgresql.org>
Subject: Re: ERROR: cannot GetMultiXactIdMembers() during recovery
Message-ID: <20150518173623.GS2523@alvh.no-ip.org>
References: <54EB3283.2080305@joh.to>
 <20150223141300.GB30784@awork2.anarazel.de>
 <5555F1E2.5080104@joh.to> <20150518164803.GP2523@alvh.no-ip.org>
 <22166.1431968387@sss.pgh.pa.us>
 <20150518171351.GR2523@alvh.no-ip.org>
 <20150518172147.GX9584@alap3.anarazel.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20150518172147.GX9584@alap3.anarazel.de>
User-Agent: Mutt/1.5.23 (2014-03-12)
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

Andres Freund wrote:
> 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@alvh.no-ip.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.

Not sure about that.  The page limits etc aren't set yet so you can't
create new multis, nor truncate appropriately, but just reading one
should have worked.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers