Re: pg_migrator and an 8.3-compatible tsvector data type - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_migrator and an 8.3-compatible tsvector data type
Date
Msg-id 1629.1243549016@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_migrator and an 8.3-compatible tsvector data type  (Josh Berkus <josh@agliodbs.com>)
Responses Re: pg_migrator and an 8.3-compatible tsvector data type  (Josh Berkus <josh@agliodbs.com>)
Re: pg_migrator and an 8.3-compatible tsvector data type  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Josh Berkus <josh@agliodbs.com> writes:
> Bruce,
>> The ordering of the lexems was changed:

> What does that get us in terms of performance etc.?

It was changed to support partial-match tsvector queries.  Without it,
a partial match query would have to scan entire tsvectors instead
of applying binary search.  I don't know if Oleg and Teodor did any
actual performance tests on the size of the hit, but it seems like
it could be pretty awful for large documents.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Clean shutdown and warm standby
Next
From: Tom Lane
Date:
Subject: Re: pg_migrator and an 8.3-compatible tsvector data type