From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Range Types and extensions |
Date: | 2011-06-06 19:18:36 |
Message-ID: | m2oc2aepkj.fsf@2ndQuadrant.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> I don't like the idea of having a capability which is not utilized
> in core. We should make it so extensions can *also* have access to
> define their own, but we should have the basics covered in core.
Well if another part of core depends on the feature set, then of course
you don't have a choice to make it an extension any more. I think
that's where I would draw the line.
> Having it as a core extension might work, but I'm not really 'sold' on
> it.
Well, core extension means built by default, part of default regression
tests and all. The regression test simply begins with the create
extension stanza, that's about it.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2011-06-06 19:24:33 | Re: reducing the overhead of frequent table locks - now, with WIP patch |
Previous Message | Simon Riggs | 2011-06-06 19:18:28 | Re: SAVEPOINTs and COMMIT performance |