On Sun, May 31, 2015 at 11:55:44AM -0400, Tom Lane wrote: > Bruce Momjian <br...@momjian.us> writes: > >> 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. > > Commit 6b700301c36e380eb4972ab72c0e914cae60f9fd is a recent real example. > Not that that should dissuade us from ever doing any reorganizations, > but it's foolish to discount back-patching costs.
Yep. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
