Skip site navigation (1) Skip section navigation (2)

Re: default_text_search_config

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: default_text_search_config
Date: 2007-10-05 02:08:39
Message-ID: 27464.1191550119@sss.pgh.pa.us (view raw or flat)
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.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tatsuo IshiiDate: 2007-10-05 02:52:36
Subject: Re: default_text_search_config
Previous:From: Uma KrishnanDate: 2007-10-05 01:37:32
Subject: Re: code documentation

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group