Re: How does the tsearch configuration get selected?

Teodor Sigaev wrote:
> So, added to my plan 
> (http://archives.postgresql.org/pgsql-hackers/2007-06/msg00618.php)
> n) single encoded files. That will touch snowball, ispell, synonym, thesaurus
>     and simple dictionaries
> n+1) use encoding names instead of locale's names in configuration

FYI, I am continuing with the documentation cleanup, though I will not
do the /ref directory until we are sure which commands will be kept.

We can later modify the documentation to match the new behavior.

---------------------------------------------------------------------------


> 
> Tom Lane wrote:
> > Teodor Sigaev <teodor@sigaev.ru> writes:
> >> But configuration for different languages might be differ, for example
> >> russian (and any cyrillic-based) configuration is differ from
> >> west-european configuration based on different character sets.
> > 
> > Sure.  I'm just assuming that the set of stopwords doesn't need to vary
> > depending on the encoding you're using for a language --- that is, if
> > you're willing to convert the encoding then the same stopword list file
> > should serve for all encodings of a given language.  Do you think this
> > might be wrong?
> > 
> >             regards, tom lane
> > 
> > ---------------------------(end of broadcast)---------------------------
> > TIP 9: In versions below 8.0, the planner will ignore your desire to
> >        choose an index scan if your joining column's datatypes do not
> >        match
> 
> -- 
> Teodor Sigaev                                   E-mail: teodor@sigaev.ru
>                                                     WWW: http://www.sigaev.ru/

--  Bruce Momjian  <bruce@momjian.us>          http://momjian.us EnterpriseDB
http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +