> > I know. My guess is the parser does not read the stop word file at
> > least with default configuration.
> Parser should not read stopword file: its deal for dictionaries.
I'll come up with more detailed info, explaining why stopword file is
> > So if a character is not ASCII, it returns 0 even if p_isalpha returns
> > 1. Is this what you expect?
> No, p_islatin should return true only for latin characters, not for national
Precise definition for "latin" in C locale please. Are you saying that
single byte encoding with range 0-7f? is "latin"? If so, it seems they
are exacty same as ASCII.
SRA OSS, Inc. Japan
> > In our case, we added JAPANESE_STOP_WORD into english.stop then:
> > select to_tsvector(JAPANESE_STOP_WORD)
> > which returns words even they are in JAPANESE_STOP_WORD.
> > And with the patches the problem was solved.
> Pls, show your configuration for lexemes/dictionaries. I suspect that you
> en_stem dictionary on for lword lexemes type. Better way is to use 'simple'
> distionary (it's support stopword the same way as en_stem does) and set it for
> nlword, word, part_hword, nlpart_hword, hword, nlhword lexeme's types. Note,
> leave unchanged en_stem for any latin word.
> Teodor Sigaev E-mail: [EMAIL PROTECTED]
---------------------------(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