From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: suitable text search configuration |
Date: | 2007-10-24 21:44:37 |
Message-ID: | 15537.1193262277@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> ... oh, I see there's a table in initdb.c
> Are we supposed to add entries to it, one for each country? I'm
> wondering if we should try to match the part before the _ using just the
> language, if the complete match fails. (i.e. match "es_CL" using just
> "es", "fr_CA" using just "fr", etc).
Actually, looking at the examples so far, I'm thinking we should just
consider the string up to the first _, period.
An alternative is to try to match the full locale (es_ES) and then try
the language (es) if that wasn't found. That would leave room to put
country-by-country exceptions in, but for the moment we'd not have any.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2007-10-24 21:58:12 | Re: suitable text search configuration |
Previous Message | Tom Lane | 2007-10-24 21:25:05 | Planner's join search strategy for clauseless joins |