Re: Range Types and extensions

From: "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Range Types and extensions
Date: 2011-06-06 18:03:06
Message-ID: 20110606180306.GC23930@rice.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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. reedstrm(at)rice(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-06-06 18:03:29 heap_hot_search_buffer refactoring
Previous Message David Fetter 2011-06-06 17:55:10 Re: permissions of external PID file