On Thu, Nov 2, 2017 at 10:38 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: >> Personally, I think it would be best to push the release out a week. > > I would only be in favor of that if there were some reason to think that > the bug is worse now than it's been in the four years since 9.3 was > released. Otherwise, we should ship the bug fixes we have on-schedule. > I think it's a very very safe bet that there are other data-loss-causing > bugs in there, so I see no good reason for panicking over this one.
Well, my thought was that delaying this release for a week would be better than either (a) doing an extra minor release just to get this fix out or (b) waiting another three months to release this fix. The former seems like fairly unnecessary work, and the latter doesn't seem particularly responsible. Users can't reasonably expect us to fix data-loss-causing bugs that we don't know about yet, but they can reasonably expect us to issue fixes promptly for ones that we do know about. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
