Re: Restore-reliability mode
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Noah Misch <noah@leadboat.com>
Cc: Bruce Momjian <bruce@momjian.us>, 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-06-03T14:18:37Z
Lists: pgsql-hackers
On 2015-06-03 09:50:49 -0400, Noah Misch wrote: > Second, I would define the subject matter as "bug fixes, testing and > review", not "restructuring, testing and review." Different code > structures are clearest to different hackers. Restructuring, on > average, adds bugs even more quickly than feature development adds > them. I can't agree with this. While I agree with not doing large restructuring for 9.5, I think we can't affort not to refactor for clarity, even if that introduces bugs. Noticeable parts of our code have to frequently be modified for new features and are badly structured at the same time. While restructuring will may temporarily increase the number of bugs in the short term, it'll decrease the number of bugs long term while increasing the number of potential contributors and new features. That's obviously not to say we should just refactor for the sake of it.
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