| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Michael Paesold <mpaesold(at)gmx(dot)at>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: How does the tsearch configuration get selected? |
| Date: | 2007-06-15 15:31:56 |
| Message-ID: | 4451.1181921516@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
Teodor Sigaev <teodor(at)sigaev(dot)ru> writes:
>> It's the to_tsvector calls
>> that built the tsvector heap column that have a locale specified or
>> implicit. We need some way of annotating the heap column about this.
> It seems too restrictive to advanced users.
Hm, are you trying to say that it's sane to have different tsvectors in
a column computed under different language settings? Maybe we're all
overthinking the problem. If the tsvector representation is presumed
language-independent then I could see this being a workable approach.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-06-15 15:39:20 | Re: How does the tsearch configuration get selected? |
| Previous Message | Robert Treat | 2007-06-15 15:27:09 | Re: The Business Case for PostgreSQL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-06-15 15:39:20 | Re: How does the tsearch configuration get selected? |
| Previous Message | Teodor Sigaev | 2007-06-15 15:16:10 | Re: How does the tsearch configuration get selected? |