| From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: tsearch2 in PostgreSQL 8.3? |
| Date: | 2007-08-14 19:26:17 |
| Message-ID: | 46C201D9.2000806@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> What is the worst consequence of mismatching configuration? Does it
> cause a system crash? A backend hang? A corrupted index? Lost data?
> Or does it, as I assume, just fail to return the exact result set that
> would be returned if the correct configuration was supplied?
Your assumption is correct.
You can mismatch configurations not just by querying in a wrong
configuration, but also by accidentally storing tsvectors generated with
different configurations in the same column (with no additional column
like Mike Rylander had to tell them apart), but it's still going to look
OK from PostgreSQL's point of view.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kenneth Marshall | 2007-08-14 20:04:37 | Re: tsearch2 in PostgreSQL 8.3? |
| Previous Message | Tom Lane | 2007-08-14 19:26:11 | Re: change name of redirect_stderr? |