Thanks to visit codestin.com
Credit goes to postgrespro.com

Request a Demo
Home   >   mailing lists

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

From [email protected] (Teodor Sigaev)
Subject pgsql: 1 Fix problem with lost precision in rank with OR-ed lexemes 2
Date
Msg-id [email protected]
Whole thread Raw
List pgsql-committers
Tree view 
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)

pgsql-committers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pgsql: Disable expanded mode only for \d
Next
From: [email protected] (Tom Lane)
Date:
Subject: pgsql: Fix race condition in multixact code: it's possible to try to