there's a lot of material on this site:
http://www.sai.msu.su/~megera/wiki/tsearch2slides
how do you create your tsvectors? If all your results have the same score
(assuming you are using two or more tokens in your tsquery) it might be that
your tsvector lacks positional information ('a b'::tsvect
Dear Jerome,
from personal experience full-text searching in PostgreSQL can be quite
powerful
but it's not simple, it requires thought, planning and coding. PostgreSQL
mainly
provides an efficient token matching mechanism supporting positional
information
and weights, but natural language processi
thanks... I guess if it really mattered it would have come up by now
(since so many interfaces are based on libpq)
toying with the idea of yet another one :-)
I have just run some tests, the number of lost bytes is always 292, no
matter how many connections are opened and closed.
I guess it's ok, then.
M.
just to say I have run into related problems on debian lenny amd64 (postgres
8.3.5, libc-2.7) and centos 5.2 (postgres 8.4.1, libc-2.5)
code as simple as this:
#include
int main()
{
PGconn *connection = PQconnectdb("user=postgres");
PQfinish(connection);
return 0;
}
gives
