Re: [CORE] postpone next week's release - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [CORE] postpone next week's release
Date
Msg-id CA+TgmoZYFXveSQO=Z4gDpvCBBCYgTFQgKec0=1EKshyJQ7kzyg@mail.gmail.com
Whole thread Raw
In response to Re: [CORE] postpone next week's release  (Magnus Hagander <magnus@hagander.net>)
Responses Re: [CORE] postpone next week's release  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
On Fri, May 29, 2015 at 3:09 PM, Magnus Hagander <magnus@hagander.net> wrote:
> Do you have any feeling of how likely people are to actually hit the
> multixact one? I've followed some of that impressive debugging you guys did,
> and I know it's a pretty critical bug if you hit it, but how wide-spread
> will it be?

That precise problem has been reported a few times, but it may not be
widespread.  I don't know.  My bigger concern is that, at present,
taking a base backup is broken.  I haven't figured out the exact
reproduction scenario, but I think it's something like this:

- begin base backup
- checkpoint happens, truncating pg_multixact
- at this point pg_multixact gets copied
- end base backup

I think what will happen on replay is that replaying the checkpoint,
it will try to reference pg_multixact files that don't exist any more
and die with a fatal error.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: RFC: Remove contrib entirely
Next
From: "Joshua D. Drake"
Date:
Subject: Re: RFC: Remove contrib entirely