Re: Problem resolved (tsearch2 inhibiting migration) - Mailing list pgsql-general

From Michael Fuhr
Subject Re: Problem resolved (tsearch2 inhibiting migration)
Date
Msg-id 20050204015955.GB63373@winnie.fuhr.org
Whole thread Raw
In response to Problem resolved (tsearch2 inhibiting migration)  (Karl Denninger <karl@denninger.net>)
Responses Re: Problem resolved (tsearch2 inhibiting migration)
List pgsql-general
On Thu, Feb 03, 2005 at 06:44:55PM -0600, Karl Denninger wrote:
>
> As it happens, there's an "untsearch2.sql" script in the contrib directory.

That reminds me: it would be useful if all contributed modules had
an unmodule.sql file.  That would simplify reloading the module if
the definitions changed, as recently happened when STRICT was added
to functions in chkpass and a few other modules; it would also make
it easy to remove the module from a particular database if it were
no longer needed.  Or is there already a way of doing this that
doesn't require you to figure out the DROP statements yourself?
Running "gmake uninstall" in the module's source directory only
removes the .so, .sql, and other installed files -- it doesn't DROP
any objects that have been created in databases.

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/

pgsql-general by date:

Previous
From: Postgre.News.Firma@spamgourmet.net
Date:
Subject: ADO adCmdStoredProc PlPgSql-SP Parameters
Next
From: Karl Denninger
Date:
Subject: Re: Problem resolved (tsearch2 inhibiting migration)