Re: [CORE] postpone next week's release
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: Michael Paquier <michael.paquier@gmail.com>
Cc: Andres Freund <andres@anarazel.de>, Robert Haas <robertmhaas@gmail.com>,
Tom Lane <tgl@sss.pgh.pa.us>, 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-31T14:03:05Z
Lists: pgsql-hackers
On Sun, May 31, 2015 at 09:50:25AM -0400, Bruce Momjian wrote: > > +1. Complexity has increased, and we are actually never at 100% sure > > that a given bug fix does not have side effects on other things, hence > > I think that a portion of this technical debt is the lack of > > regression test coverage, for both existing features and platforms > > (like Windows). The thing is that complexity has increased, but for > > example for many features we lack test coverage, thinking mainly > > replication-related stuff here. Of course we will never get to a level > > of 100% of confidence with just the test coverage and the buildfarm, > > but we should at least try to get closer to such a goal. > > FYI, I realize that one additional thing that has discouraged code > reorganization is the additional backpatch overhead. I think we now > need to accept that our reorganization-adverse approach might have cost > us some reliability, and that reorganization is going to add work to > backpatching. Actually, code reorganization in HEAD might cause backpatching to be more buggy, reducing reliability --- obviously we need to have a discussion about that. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. +
Commits
-
Add Valgrind buffer access instrumentation.
- 1e0dfd166b3f 14.0 landed
-
Fix wrong merge resolution making pg_receivexlog fail in 9.2.
- 6b700301c36e 9.2.11 cited