pgsql: 1 Fix problem with lost precision in rank with OR-ed lexemes 2

From: teodor(at)svr1(dot)postgresql(dot)org (Teodor Sigaev)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: 1 Fix problem with lost precision in rank with OR-ed lexemes 2
Date: 2005-10-28 13:05:07
Message-ID: 20051028130507.43E28DB217@svr1.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
1 Fix problem with lost precision in rank with OR-ed lexemes
2 Allow tsquery_in to input void tsquery: resolve dump/restore problem with tsquery

Modified Files:
--------------
pgsql/contrib/tsearch2:
query.c (r1.17 -> r1.18)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/tsearch2/query.c.diff?r1=1.17&r2=1.18)
rank.c (r1.10 -> r1.11)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/tsearch2/rank.c.diff?r1=1.10&r2=1.11)
pgsql/contrib/tsearch2/expected:
tsearch2.out (r1.12 -> r1.13)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/tsearch2/expected/tsearch2.out.diff?r1=1.12&r2=1.13)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2005-10-28 17:27:30 pgsql: Fix race condition in multixact code: it's possible to try to
Previous Message Bruce Momjian 2005-10-28 02:39:32 Re: pgsql: Disable expanded mode only for \d