From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | 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-14 20:41:05 |
Message-ID: | 200708142041.l7EKf5b07214@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> Bruce Momjian wrote:
>
> > Basically, the default GUC doesn't work because of:
> >
> > error prone
> > if super-user only, non-super-user doesn't work on restore
> > if non-super-user, can cause mismatch (perhaps this is the best
> > option), and restore still a problem (no storage of config in
> > indexes or tables)
>
> I haven't really seen anyone else arguing about this. I wonder whether
> you are being overly zealous about it.
Uh, OK, but no one has told me how a database restore without a
configuration name would work, so I am all ears.
CREATE INDEX ii on x(to_tsvector(col))
There is nothing that says what configuration that index should use
except the default setting, and if that is different in the restore
database, you have problems. Same for a trigger that calls to_tsvector
and is restored into a different database.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Rylander | 2007-08-14 20:47:13 | Re: tsearch2 in PostgreSQL 8.3? |
Previous Message | Bruce Momjian | 2007-08-14 20:38:51 | Re: default_text_search_config and expression indexes |