Re: How does the tsearch configuration get selected?

> Hm, are you trying to say that it's sane to have different tsvectors in
> a column computed under different language settings?  Maybe we're all

Yes, I think so.

That might have sense for close languages. Norwegian languages has two dialects 
and one of them has advanced rules for compound words, russian and ukranian has 
similar rules etc. Operation @@ is language (and encoding) independent, it use 
just strcmp call.

Most often usecase for mixing configuration is somewhere described by me in 
thread using two different configuration for indexing (tsvector creation) and 
search (tsquery creation). BTW, thesaurus dictionary could be used for similar 
reasons in search only configuration.

OpenFTS doesn't use tsearch2 configuration at all, it has such infrastructure 
itself - so, tsvector shouldn't have any information about configuration.

Most often change of configuration is a adding new stop words, which doesn't 
affect correctness of search. Removing stop words cause impossibility to find 
already indexed documents with query contains only removed stop-words.


> overthinking the problem.  If the tsvector representation is presumed
> language-independent then I could see this being a workable approach.

Actually, we should allow to only 'compatible' changes of configuration but it 
very hard (or even impossible) to formulate rules about that. Any dictionary has  its specific dictinitoption changes
tobecome incompatible with itself, the 
 
same is to compatibility between two dictionaries, list of dictionaries.

In practice, we didn't see any disasters after changes in configuration - until 
reindexing search becomes less punctual.


-- 
Teodor Sigaev                                   E-mail: teodor@sigaev.ru
  WWW: http://www.sigaev.ru/