pgsql: Fix misuse of Lossy Counting (LC) algorithm in

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix misuse of Lossy Counting (LC) algorithm in
Date: 2010-05-30 21:59:03
Message-ID: 20100530215903.0D1B47541D2@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Fix misuse of Lossy Counting (LC) algorithm in compute_tsvector_stats().

We must filter out hashtable entries with frequencies less than those
specified by the algorithm, else we risk emitting junk entries whose
actual frequency is much less than other lexemes that did not get
tabulated. This is bad enough by itself, but even worse is that
tsquerysel() believes that the minimum frequency seen in pg_statistic is a
hard upper bound for lexemes not included, and was thus underestimating
the frequency of non-MCEs.

Also, set the threshold frequency to something with a little bit of theory
behind it, to wit assume that the input distribution is approximately
Zipfian. This might need adjustment in future, but some preliminary
experiments suggest that it's not too unreasonable.

Back-patch to 8.4, where this code was introduced.

Jan Urbanski, with some editorialization by Tom

Modified Files:
--------------
pgsql/src/backend/tsearch:
ts_typanalyze.c (r1.8 -> r1.9)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/tsearch/ts_typanalyze.c?r1=1.8&r2=1.9)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2010-05-30 21:59:10 pgsql: Fix misuse of Lossy Counting (LC) algorithm in
Previous Message Tom Lane 2010-05-30 18:10:41 pgsql: Change the notation for calling functions with named parameters