From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Teodor Sigaev" <teodor(at)sigaev(dot)ru>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Michael Paesold" <mpaesold(at)gmx(dot)at>, "Joshua D(dot) Drake" <jd(at)commandprompt(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:57:05 |
Message-ID: | 878xalcisu.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-hackers |
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> It's not really the index's problem; IIUC the behavior of the gist and
> gin index opclasses is not locale-specific. 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.
>
> In the case of a functional index you can expose the locale:
>
> create index ... (to_tsvector('english'::regconfig, mytextcol))
Maybe there should be a different type for each locale.
I'm not exactly following this thread so I'm not entirely sure whether that
would actually fit well but it's just a thought I had.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2007-06-15 16:07:34 | Re: How does the tsearch configuration get selected? |
Previous Message | nhrcommu | 2007-06-15 15:49:08 | Re: The Business Case for PostgreSQL |
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2007-06-15 16:07:34 | Re: How does the tsearch configuration get selected? |
Previous Message | Simon Riggs | 2007-06-15 15:39:36 | Re: tsearch_core patch: permissions and security issues |