| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
| Subject: | Re: tsearch2 in PostgreSQL 8.3? |
| Date: | 2007-08-17 23:06:15 |
| Message-ID: | 200708171606.15909.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce,
> 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. 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.
Sticking the config name at the beginning of the field would allow for the
use of single-parameter functions, and default_config would only be used
for SELECT queries. Backup/restore issues should go away completely ...
EXCEPT this would introduce issues if the config is changed or deleted
after being used. However, I'd imagine that we have those anyway --
certainly we would at restore time.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-08-17 23:19:10 | Re: tsearch2 in PostgreSQL 8.3? |
| Previous Message | Ron Mayer | 2007-08-17 22:32:54 | Re: tsearch2 in PostgreSQL 8.3? |