Tatsuo Ishii <ishii(at)postgresql(dot)org> writes:
> When I run initdb -E EUC_JP --no-locale, I found following in my
> 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.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Tatsuo Ishii||Date: 2007-10-05 02:52:36|
|Subject: Re: default_text_search_config |
|Previous:||From: Uma Krishnan||Date: 2007-10-05 01:37:32|
|Subject: Re: code documentation|