Back branch update releases this week; beta postponed
In view of the recently-discovered data loss bug in pg_upgrade,
it seems imperative to push out update releases fixing that as soon
as possible. The core team has therefore decided to wrap back-branch
update releases this Thursday for release Monday 4/18.
We were previously targeting wrapping 9.1beta1 on Thursday, but it
would not be a good idea to do that at the same time as the update
releases. Aside from the risk of overburdening packagers, we would
like to make a PR splash for the beta release, and not dilute that
message with the update-releases-to-fix-data-loss issue. And with
assorted major contributors off at a conference this week, it was
far from clear that we'd be ready for beta by Thursday anyway.
Accordingly, the beta release will have to be postponed.
Since the following weekend is Easter holidays for many, it's not
very practical to consider a one-week slip for beta. The tentative
plan is to slip two weeks (ie, beta wrap will be April 28). We could
possibly do something creative with a midweek release date, but that
could be problematic from both packagers' and PR standpoints.
regards, tom lane
--On 10. April 2011 13:53:52 -0400 Tom Lane <tgl@sss.pgh.pa.us> wrote:
In view of the recently-discovered data loss bug in pg_upgrade,
it seems imperative to push out update releases fixing that as soon
as possible. The core team has therefore decided to wrap back-branch
update releases this Thursday for release Monday 4/18.
Hmm, I would like to see the patch for
<http://archives.postgresql.org/pgsql-bugs/2011-03/msg00261.php>
going in for 8.4.8. We are currently running a patched RPM on a production
standby on the customers site, and it seems to work well, no hangs occured so
far.
--
Thanks
Bernd
Bernd Helmle <mailings@oopsware.de> writes:
--On 10. April 2011 13:53:52 -0400 Tom Lane <tgl@sss.pgh.pa.us> wrote:
The core team has therefore decided to wrap back-branch
update releases this Thursday for release Monday 4/18.
Hmm, I would like to see the patch for
<http://archives.postgresql.org/pgsql-bugs/2011-03/msg00261.php>
going in for 8.4.8.
Simon, was there a reason you only back-patched that to 9.0?
regards, tom lane
--On 12. April 2011 10:58:25 -0400 Tom Lane <tgl@sss.pgh.pa.us> wrote:
Hmm, I would like to see the patch for
<http://archives.postgresql.org/pgsql-bugs/2011-03/msg00261.php>
going in for 8.4.8.Simon, was there a reason you only back-patched that to 9.0?
So it seems we have shipped 8.4.8 without a fix for this ?
--
Thanks
Bernd
Tom Lane wrote:
Bernd Helmle <mailings@oopsware.de> writes:
--On 10. April 2011 13:53:52 -0400 Tom Lane <tgl@sss.pgh.pa.us> wrote:
The core team has therefore decided to wrap back-branch
update releases this Thursday for release Monday 4/18.Hmm, I would like to see the patch for
<http://archives.postgresql.org/pgsql-bugs/2011-03/msg00261.php>
going in for 8.4.8.Simon, was there a reason you only back-patched that to 9.0?
Was this addressed?
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
On Wed, Sep 7, 2011 at 2:43 AM, Bruce Momjian <bruce@momjian.us> wrote:
Tom Lane wrote:
Bernd Helmle <mailings@oopsware.de> writes:
--On 10. April 2011 13:53:52 -0400 Tom Lane <tgl@sss.pgh.pa.us> wrote:
The core team has therefore decided to wrap back-branch
update releases this Thursday for release Monday 4/18.Hmm, I would like to see the patch for
<http://archives.postgresql.org/pgsql-bugs/2011-03/msg00261.php>
going in for 8.4.8.Simon, was there a reason you only back-patched that to 9.0?
Was this addressed?
Fix applied, following positive feedback in production testing.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services