Horton

Re: postpone next week's release

David G. Johnston <david.g.johnston@gmail.com>

View thread View on postgr.es
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Peter Geoghegan <pg@heroku.com>, Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>, Andres Freund <andres@anarazel.de>, Stephen Frost <sfrost@snowman.net>, Magnus Hagander <magnus@hagander.net>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, pgsql-core <pgsql-core@postgresql.org>
Date: 2015-05-31T02:40:07Z
Lists: pgsql-hackers 
On Saturday, May 30, 2015, Bruce Momjian <bruce@momjian.us> wrote:

> On Sat, May 30, 2015 at 12:26:11PM -0700, Peter Geoghegan wrote:
> > On Sat, May 30, 2015 at 5:56 AM, Bruce Momjian <bruce@momjian.us
> <javascript:;>> wrote:
> > > Frankly, based on how I feel now, I would have no problem doing 9.5 in
> > > 2016 and saying we have a lot of retooling to do.  We could say we have
> > > gotten too far out ahead of ourselves and we need to regroup and
> > > restructure the code.
> >
> > I wouldn't mind doing that, but I think it's premature to conclude
> > that it's necessary to wait quite that long to release.
>
> I agree it probably wouldn't take until 2016, but if does take until
> 2016, we have to be fine with that.  What I am saying is we can't just
> continue to focus on hitting target dates and assume everything will be
> fine, because it isn't.
>
>
On a slightly tangential note: I'm not prepared to defend doing so but it
seems worth at least considering whether we should continue supporting 9.0
beyond this October.

I don't think it should be be de-supported until at least a couple of 9.5
point releases have been found to be stable.

David J.

Commits

  1. Add Valgrind buffer access instrumentation.

  2. Fix wrong merge resolution making pg_receivexlog fail in 9.2.