Re: tsearch2 in PostgreSQL 8.3? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: tsearch2 in PostgreSQL 8.3?
Date
Msg-id 5812.1187281983@sss.pgh.pa.us
Whole thread Raw
In response to Re: tsearch2 in PostgreSQL 8.3?  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: tsearch2 in PostgreSQL 8.3?  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
Gregory Stark <stark@enterprisedb.com> writes:
> Is there a null configuration which could be the default for the casts?

If we did that then there would be no point in having a GUC variable,
because it wouldn't control anything.

While that is certainly an alternative solution, I think it's riskier
than having the GUC variable and just preventing (or at least
discouraging) people from relying on it in their index definitions.
The problem is that people will resort to "ALTER CONFIGURATION default"
to tune their setups, and anytime you make a nontrivial change that way,
you run the risk of breaking your existing indexes.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: cvsweb busted (was Re: [COMMITTERS] pgsql: Repair problems occurring when multiple RI updates have to be)
Next
From: Alvaro Herrera
Date:
Subject: Re: build farm failures