| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| 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:36:23 |
| Message-ID: | 20150518173623.GS2523@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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(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.
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-05-18 17:37:20 | Re: How does MSVC's fetchRegressOpts() work at all? |
| Previous Message | Andrew Dunstan | 2015-05-18 17:29:45 | Re: jsonb concatenate operator's semantics seem questionable |