On Mon, Jun 06, 2011 at 12:53:49PM -0400, Robert Haas wrote: > > I don't have clear feeling on this question in general, but if we're > going to break this up into pieces, it's important that they be > logical pieces. Putting half the feature in core and half into an > extension just because we can will simplify complicate code > maintenance to no good end. The snowball effect is something to > avoid, and we need to watch out for that, but if the upshot of putting > part of it in core is that the core code can no longer be understood > or maintained because it depends heavily on a bunch of non-core code, > that's not helpful. > And concretely, code paths that cannot be exercised easily from core-only code will not get regression tested, and will therefore rot.
Ross -- Ross Reedstrom, Ph.D. reeds...@rice.edu Systems Engineer & Admin, Research Scientist phone: 713-348-6166 Connexions http://cnx.org fax: 713-348-3665 Rice University MS-375, Houston, TX 77005 GPG Key fingerprint = F023 82C8 9B0E 2CC6 0D8E F888 D3AE 810E 88F0 BEDE -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
