From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | ishii(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: default_text_search_config |
Date: | 2007-10-05 02:52:36 |
Message-ID: | 20071005.115236.48462209.t-ishii@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Tatsuo Ishii <ishii(at)postgresql(dot)org> writes:
> > When I run initdb -E EUC_JP --no-locale, I found following in my
> > postgresql.conf:
>
> > default_text_search_config = 'pg_catalog.english'
>
> > The manual says:
>
> > default_text_search_config (string)
>
> > Selects the text search configuration that is used by those
> > variants of the text search functions that do not have an explicit
> > argument specifying the configuration. See Chapter 12 for further
> > information. The built-in default is pg_catalog.simple, but initdb
> > will initialize the configuration file with a setting that
> > corresponds to the chosen lc_ctype locale, if a configuration
> > matching that locale can be identified.
>
> > So I thought the initial value for it should be pg_catalog.simple,
> > rather than pg_catalog.english. If this is not a bug, what is the
> > idea behind lc_ctype = C corresponds to 'pg_catalog.english'?
> > When is pg_catalog.simple supposed to be used?
>
> Well, that documentation is correct as far as it goes; what it doesn't
> say is that initdb's mapping table explicitly maps C/POSIX locales to
> english. It seems like a reasonable default on this side of the water,
> but maybe I'm being too North-American-centric.
Ok. Are you going to to add "initdb's mapping table explicitly maps
C/POSIX locales to english" to the doc? If no, I can do that part.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-10-05 03:02:11 | Re: default_text_search_config |
Previous Message | Tom Lane | 2007-10-05 02:08:39 | Re: default_text_search_config |