Re: default_text_search_config and expression indexes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Mike Rylander <mrylander(at)gmail(dot)com>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: default_text_search_config and expression indexes
Date: 2007-08-14 21:58:21
Message-ID: 12437.1187128701@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-hackers

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Bruce Momjian escribi:
>> What has really hurt the default GUC idea is how to do restores from a
>> pg_dump.

> I guess what should happen is that pg_dump should include a
> SET default_text_search_config = 'foo'
> just before the CREATE INDEX, like we do for other variables.

The nasty cases are in data-only dumps, that is, where you're trying to
load data into a table with pre-existing indexes or triggers. A SET
like the above is at least as likely to be wrong as right, if the index
or trigger depends on it to tell it what to do.

regards, tom lane

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Gregory Stark 2007-08-14 22:17:19 Re: default_text_search_config and expression indexes
Previous Message Bob Zurek 2007-08-14 21:35:59 12 Silver Bullets

Browse pgsql-hackers by date

  From Date Subject
Next Message Kris Jurka 2007-08-14 22:06:46 CVS corruption/mistagging?
Previous Message Bruce Momjian 2007-08-14 21:43:13 Re: tsearch2 in PostgreSQL 8.3?