From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | default_text_search_config |
Date: | 2007-10-05 01:17:29 |
Message-ID: | 20071005.101729.77701208.t-ishii@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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?
--
Tatsuo Ishii
SRA OSS, Inc. Japan
From | Date | Subject | |
---|---|---|---|
Next Message | Uma Krishnan | 2007-10-05 01:37:32 | Re: code documentation |
Previous Message | Tom Lane | 2007-10-05 01:09:15 | Re: tsearch2 wrapper |