"Tom Lane" <[EMAIL PROTECTED]> 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

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not

Reply via email to