| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:16:10 |
| Message-ID: | 4672AD3A.1040302@sigaev.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
> It's not really the index's problem; IIUC the behavior of the gist and
> gin index opclasses is not locale-specific.
Right
> 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.
>
> In the case of a functional index you can expose the locale:
>
> create index ... (to_tsvector('english'::regconfig, mytextcol))
>
> but there's still the problem that the planner cannot match that to
> a query specified as just WHERE to_tsvector(mytextcol) @@ query.
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Treat | 2007-06-15 15:27:09 | Re: The Business Case for PostgreSQL |
| Previous Message | Teodor Sigaev | 2007-06-15 15:15:16 | Re: How does the tsearch configuration get selected? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-06-15 15:31:56 | Re: How does the tsearch configuration get selected? |
| Previous Message | Teodor Sigaev | 2007-06-15 15:15:16 | Re: How does the tsearch configuration get selected? |