Re: tsearch2 in PostgreSQL 8.3?
От | Bruce Momjian |
---|---|
Тема | Re: tsearch2 in PostgreSQL 8.3? |
Дата | |
Msg-id | 200708142041.l7EKf5b07214@momjian.us обсуждение исходный текст |
Ответ на | Re: tsearch2 in PostgreSQL 8.3? (Alvaro Herrera <alvherre@commandprompt.com>) |
Ответы |
Re: tsearch2 in PostgreSQL 8.3?
|
Список | 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@momjian.us> http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
В списке pgsql-hackers по дате отправления: