Re: tsearch2 in PostgreSQL 8.3?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: "Michael Paesold" <mpaesold(at)gmx(dot)at>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Mike Rylander" <mrylander(at)gmail(dot)com>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: tsearch2 in PostgreSQL 8.3?
Date: 2007-08-16 16:33:03
Message-ID: 5812.1187281983@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Gregory Stark <stark(at)enterprisedb(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2007-08-16 16:37:54 Re: build farm failures
Previous Message Magnus Hagander 2007-08-16 16:29:22 Re: cvsweb busted (was Re: pgsql: Repair problems occurring when multiple RI updates have to be)