Date: Mon, 18 May 2015 17:45:46 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Simon Riggs <simon@2ndQuadrant.com>
Cc: Andres Freund <andres@2ndquadrant.com>, Marko Tiikkaja <marko@joh.to>,
 hackers <pgsql-hackers@postgresql.org>
Subject: Re: ERROR: cannot GetMultiXactIdMembers() during recovery
Message-ID: <20150518204546.GU2523@alvh.no-ip.org>
References: <54EB3283.2080305@joh.to>
 <20150223141300.GB30784@awork2.anarazel.de>
 <20150515180335.GE2523@alvh.no-ip.org>
 <CANP8+jLv=rFMCXM+V8m9WiTT+8tspmyeh2FtxC6u+3nW6shoTw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CANP8+jLv=rFMCXM+V8m9WiTT+8tspmyeh2FtxC6u+3nW6shoTw@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

Simon Riggs wrote:
> On 15 May 2015 at 19:03, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
> 
> > Andres Freund wrote:
> >
> > > Alternatively we could make MultiXactIdIsRunning() return false < 9.3
> > > when in recovery. I think that'd end up fixing things, but it seems
> > > awfully fragile to me.
> >
> > Hm, why fragile?  It seems a pretty decent answer -- pre-9.3, it's not
> > possible for a tuple to be "locked" in recovery, is it?  I mean, in the
> > standby you can't lock it nor update it; the only thing you can do is
> > read (select), and that is not affected by whether there is a multixact
> > in it.
> 
> It can't return true and won't ever change for <9.3 so I don't see what the
> objection is.

Pushed.

-- 
Á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