Re: Problem resolved (tsearch2 inhibiting migration)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Karl Denninger <karl(at)denninger(dot)net>
Cc: Michael Fuhr <mike(at)fuhr(dot)org>, pgsql-general(at)postgresql(dot)org
Subject: Re: Problem resolved (tsearch2 inhibiting migration)
Date: 2005-02-04 03:20:47
Message-ID: 9787.1107487247@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Karl Denninger <karl(at)denninger(dot)net> writes:
> I agree with this - what would be even better would be a way to create
> 'subclasses' for things like this, which could then be 'included' easily.

We could decree that a contrib module's script should create a schema
and shove everything it makes into that schema. Then "DROP SCHEMA CASCADE"
is all you need to get rid of it. However, you'd probably end up having
to add this schema to your search path to use the module conveniently.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Karl Denninger 2005-02-04 03:56:47 Re: Problem resolved (tsearch2 inhibiting migration)
Previous Message Karl Denninger 2005-02-04 02:25:12 Re: Problem resolved (tsearch2 inhibiting migration)