| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | jd(at)commandprompt(dot)com |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Josh Berkus <josh(at)agliodbs(dot)com>, Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ALTER EXTENSION ... UPGRADE; |
| Date: | 2010-12-10 20:54:08 |
| Message-ID: | 29250.1292014448@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> On Fri, 2010-12-10 at 15:42 -0500, Andrew Dunstan wrote:
>> On 12/10/2010 03:24 PM, Josh Berkus wrote:
>>> Also, once extensions and pgxn are operating full swing, I see contrib
>>> going away anyway ...
>> We've heard this before, but I'm still quite skeptical about it. Quite
>> apart from anything else we should keep enough extensions in core to
>> test the extension mechanism, as well as to provide examples as part of
>> the base distribution. Some (e.g. hstore and citext) should probably
>> move into core. Others like pgcrypto are probably in just the right
>> place as they are.
> I hope that contrib goes away. I agree with your assertion that things
> like hstore and citext shoudl be in core but it is my hope that with
> extensions and pgxn, there will be no reason for contrib to exist at
> all.
I agree with Andrew --- we're going to need a collection of "standard
extensions" if only for testing purposes. It may someday not be called
contrib, but it'll still be there.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2010-12-10 21:50:59 | Re: ALTER EXTENSION ... UPGRADE; |
| Previous Message | Tom Lane | 2010-12-10 20:48:49 | Re: ALTER EXTENSION ... UPGRADE; (was: Extensions, patch v16) |