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

From Tom Lane
Subject Re: [CORE] postpone next week's release
Date
Msg-id 27262.1432928581@sss.pgh.pa.us
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  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> On Fri, May 29, 2015 at 9:32 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I think there's no way that we wait more than one additional week to push
>> the fsync fix.  So the problem is not with scheduling the update releases,
>> it's with whether we can also fit in a 9.5 beta release before PGCon.

> I think 9.5 beta has to stand back. The question is what we do with the
> potentially two minor releases. Then we can slot in the beta whenever.

> If we do the minor as currently planned, can we do another one the week
> after to deal with the multixact issues? (scheduling wise we're going to
> have to do one the week after *regardless*, the question is if we can make
> two different ones, or if we need to fold them into one)

I suppose we could, but it doubles the amount of release gruntwork
involved, and it doesn't exactly make us look good to our users either.

I believe Christoph indicated that he was going to cherry-pick the fsync
patch and push out an intermediate Debian package with that fix, so at
least for that community there is not an urgent reason to get out a set
of releases with only the fsync fixes and not the multixact fixes.  I'm
not clear though on how many of the other reports we heard came from
Debian users.  (Some of them did, but maybe not all.)
        regards, tom lane



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Need Force flag for pg_drop_replication_slot()
Next
From: Stephen Frost
Date:
Subject: Re: [CORE] postpone next week's release