Re: Modifying and solidifying contrib - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: Modifying and solidifying contrib
Date
Msg-id A9A9F043-5F1F-402C-A435-ED2D8F2945C4@decibel.org
Whole thread Raw
In response to Re: Modifying and solidifying contrib  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Modifying and solidifying contrib  (Paul Ramsey <pramsey@refractions.net>)
List pgsql-hackers
On Feb 5, 2007, at 11:19 AM, Andrew Dunstan wrote:
> Jim Nasby wrote:
>> There was also mention of having a means to tell pg_dump not to  
>> dump extensions...
> What's the use case for that? What will we do if there are db  
> objects that depend on some extensions? Given that there will be  
> some uninstall support, this one seems less necessary.

In addition to Martijn's tsearch case, there's also PostGIS. And I  
believe this is a pretty big pain for them.

> I really think we should approach this by not trying to do  
> everything at once.

That's fine; I just wanted to point out the use case while lists were  
being made.
--
Jim Nasby                                            jim@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)




pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: doxygen.postgresql.org
Next
From: Jim Nasby
Date:
Subject: Re: [PATCHES] Fix "database is ready" race condition