On Wed, Sep 7, 2011 at 2:43 AM, Bruce Momjian br...@momjian.us wrote:
Tom Lane wrote:
Bernd Helmle maili...@oopsware.de writes:
--On 10. April 2011 13:53:52 -0400 Tom Lane t...@sss.pgh.pa.us wrote:
The core team has therefore decided to wrap back-branch
update releases this Thursday for
Tom Lane wrote:
Bernd Helmle maili...@oopsware.de writes:
--On 10. April 2011 13:53:52 -0400 Tom Lane t...@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
--On 12. April 2011 10:58:25 -0400 Tom Lane t...@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
--On 10. April 2011 13:53:52 -0400 Tom Lane t...@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
Bernd Helmle maili...@oopsware.de writes:
--On 10. April 2011 13:53:52 -0400 Tom Lane t...@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
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
