Re: Problem resolved (tsearch2 inhibiting migration)

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: Karl Denninger <karl(at)denninger(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Problem resolved (tsearch2 inhibiting migration)
Date: 2005-02-04 01:59:55
Message-ID: 20050204015955.GB63373@winnie.fuhr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Karl Denninger 2005-02-04 02:25:12 Re: Problem resolved (tsearch2 inhibiting migration)
Previous Message True211 2005-02-04 01:47:18 Re: [OT] PostgreSQL: bytea help needed.