| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | josh(at)agliodbs(dot)com |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
| Subject: | Re: tsearch2 in PostgreSQL 8.3? |
| Date: | 2007-08-17 23:19:10 |
| Message-ID: | 11478.1187392750@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
>> Oh, so you want the config inside each tsvector value. Interesting
>> idea.
> Yeah, hasn't anyone suggested this before? It seems like the obvious
> solution.
It might be an obvious solution, but to some other problem than the one
we have. The problem we are trying to address is how to know which
config to use to construct a *new* tsvector.
> A TSvector constructed with en_US is NOT the same as a vector
> constructed with fr_FR and it's silly to pretend that they are comparable.
Um, actually I think Oleg and Teodor believe that they *are* comparable.
If we try to force them not to be then we'll break multi-language
situations.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2007-08-17 23:40:43 | Re: tsearch2 in PostgreSQL 8.3? |
| Previous Message | Josh Berkus | 2007-08-17 23:06:15 | Re: tsearch2 in PostgreSQL 8.3? |