I apologize if I'm being dense, but I'm not completely following the
explanation. It is true that my pg_ts_cfg.locale is set to en_US.UTF-8.
It was my understanding that specifying "default" as in
UPDATE t SET idxB=to_tsvector('default', b);
should give tsearch enough information.
It is not clear to me why the first time works, but not the second time
with almost identical statements.
I thought that I only had to follow the procedure in the docs if I want
to do the following:
UPDATE t SET idxB=to_tsvector(b); -- no 'default'
Perhaps I am wrong about this?
> -----Original Message-----
> From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-
> owner@postgresql.org] On Behalf Of Andrew J. Kopciuch
> Sent: Wednesday, November 23, 2005 12:08 AM
> To: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] tsearch2: more than one index per table?
>
> On Tuesday 22 November 2005 21:45, Rick Schumeyer wrote:
> > Is there something in tsearch2 that prevents more than one index per
> table?
> >
> > I would like an index on field A, and a separate index on field B.
> >
> > The index builds fine for A, but gives an error for B. The error text
> is
> >
> >
> >
> > ERROR: could not find tsearch config by locale
> >
> >
>
>
> This is not a problem with the index creation ... your tsearch2
> installation
> is not configured for the locale your server is running.
>
> http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/docs/tsearch-V2-
> intro.html
>
> See the section "TSEARCH2 CONFIGURATION". It explains, and has examples
> on
> how to set this up.
