mirror of
https://github.com/postgres/postgres.git
synced 2026-04-20 22:00:13 -04:00
possible (ie, whenever the tsquery is a constant), even when no statistics are available for the tsvector. For example, foo @@ 'a & b'::tsquery can be expected to be more selective than foo @@ 'a'::tsquery, whether or not we know anything about foo. We use DEFAULT_TS_MATCH_SEL as the assumed selectivity of individual query terms when no stats are available, then combine the terms according to the query's AND/OR structure as usual. Per experimentation with Artur Dabrowski's example. (The fact that there are no stats available in that example is a problem in itself, but nonetheless tsmatchsel should be smarter about the case.) Back-patch to 8.4 to keep all versions of tsmatchsel() in sync. |
||
|---|---|---|
| .. | ||
| dict.c | ||
| dict_ispell.c | ||
| dict_simple.c | ||
| dict_synonym.c | ||
| dict_thesaurus.c | ||
| hunspell_sample.affix | ||
| ispell_sample.affix | ||
| ispell_sample.dict | ||
| Makefile | ||
| regis.c | ||
| spell.c | ||
| synonym_sample.syn | ||
| thesaurus_sample.ths | ||
| to_tsany.c | ||
| ts_locale.c | ||
| ts_parse.c | ||
| ts_selfuncs.c | ||
| ts_typanalyze.c | ||
| ts_utils.c | ||
| wparser.c | ||
| wparser_def.c | ||