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 03:02:11
Message-ID: 28422.1191553331@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Tatsuo Ishii <ishii(at)postgresql(dot)org> writes:
>> 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.

Before we worry about documenting the behavior, are you happy
about it?  What could be done differently?  I'm wondering if it makes
any sense to consider the specified database encoding while making
the text-search decision ...

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tatsuo IshiiDate: 2007-10-05 03:54:04
Subject: Re: default_text_search_config
Previous:From: Tatsuo IshiiDate: 2007-10-05 02:52:36
Subject: Re: default_text_search_config

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