Date: Fri, 29 May 2015 15:31:46 -0400
From: Stephen Frost <sfrost@snowman.net>
To: Magnus Hagander <magnus@hagander.net>
Cc: Robert Haas <robertmhaas@gmail.com>,
 "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>,
 pgsql-core <pgsql-core@postgresql.org>
Subject: Re: [CORE] postpone next week's release
Message-ID: <20150529193146.GI26667@tamriel.snowman.net>
References: 
 <CA+TgmoY-OUbRAqZ7Rgdwb-_CTBbY=fkR93sgPrJaFfR8oojeCw@mail.gmail.com>
 <20150529185431.GG26667@tamriel.snowman.net>
 <CABUevExb+p3OGFBAMTc2s0tuuygkmnca_BV6Qe0hACvRmgyb1w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="CVXpx251GNNJP8Zs"
Content-Disposition: inline
In-Reply-To: 
 <CABUevExb+p3OGFBAMTc2s0tuuygkmnca_BV6Qe0hACvRmgyb1w@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org


--CVXpx251GNNJP8Zs
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Magnus Hagander (magnus@hagander.net) wrote:
> On Fri, May 29, 2015 at 8:54 PM, Stephen Frost <sfrost@snowman.net> wrote:
>=20
> > * Robert Haas (robertmhaas@gmail.com) wrote:
> > > I think we should postpone next week's release.  I have been hard at
> > > work on the multixact-related bugs that were reported in 9.4.2 and
> > > 9.3.7, and the subsequent bugs found by code-reading, but getting them
> > > all fixed by Monday doesn't seem realistic.  Such fixes should have
> > > careful review, and not be dashed into the tree under time pressure.
> > >
> > > We could do the release anyway to relieve the pain caused by the
> > > fsync-pgdata hard-failure problem, but it seems to me that if we do
> > > that, we're just going to end up having to do yet another release
> > > almost right away.  I think it would be better to wait and do one
> > > release that fixes both sets of issues.
> >
> > Agreed.
> >
> > I just caution that we appreciate PGCon coming up and that we do our
> > best to avoid running into a case where we have to push it further due
> > to everyone being at the conference.
>=20
> If we plan it, we certainly *can* make a release during pgcon. If that's
> what the reasonable timing comes down to, I think getting these fixes out
> definitely has to be considered more important than the conference, so a
> few of us will just have to take a break...

I don't disagree with you about any of that, just wanted to make mention
of the timing.

	Thanks!

		Stephen

--CVXpx251GNNJP8Zs
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJVaL6iAAoJEO1sijiDR2RVldgP/2WtLrpsr8Z1KYEnWaDBEXOa
3vNZEVBedCJ8NsCc/CKs08imdZJ/5/pi3aY08Zs12limQE52dBUdBeMputi9i3Fo
wMg2nF9wX6ZiWRE9tLbGLuTtDM18B8yfEJzZmPVtdwHENcGw3J+LaiXZOCw2eIuO
4Vo+4XiW/FL8IlmgGwaS+jED51UnD8+xtuasE7AW+kveM2pUZ9tJLFCMoRTJQQfH
tY5hmE9ns6qjdv5n8BYEadV4AGaGButYCLDIm5r4YB5ev99u0tsZkR8JnAR+v8yC
4ny/QIku/SF4ewD3LdvD+0055k0mkQ7jvfioDO0YhIOX/SiaAZps11wDJYupUF00
E77FC8LUjEcrq6k0yZVuV2+9DKCYUB6ZmH2fTaaEBGA7R96qegG3h6vtJNwHgKfw
ledeMumWLiVfXZld8VU3C+GApcrDbnARTmhvsG9ff462/cCIC5JvxvAmBjwnkYdS
ihiWTOlWgmwTwV/8yOom3UhtvGQMNV7XAEH6qs+Wi9i86CkICu+XMyBKkNST+fnM
jBKHCY2eusPcuNkYHw/ln/QLgmi+dD5U/ZcEdtUHhcRjl/AlpZ7PNUVY5aKM6PYH
TBb2A6dr5/262y0X8Dg7UhGq1JpSTmjvYKHaaJCc4g3NLAW9G4bWGPIIq/8aR5QM
EQ08jn/Ca42fD/99r3Hn
=vjfh
-----END PGP SIGNATURE-----

--CVXpx251GNNJP8Zs--