Re: Full text search with ORDER BY performance issue - Mailing list pgsql-performance

From Tom Lane
Subject Re: Full text search with ORDER BY performance issue
Date
Msg-id 17530.1248877344@sss.pgh.pa.us
Whole thread Raw
In response to Re: Full text search with ORDER BY performance issue  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Full text search with ORDER BY performance issue
List pgsql-performance
Robert Haas <robertmhaas@gmail.com> writes:
> If love is an uncommon word, there's no help for queries of this type
> being slow unless the GIN index can return the results in order.  But
> if love is a common word, then it would be faster to do an index scan
> by timestamp on the baserel and then treat comment_tsv @@
> plainto_tsquery('love') as a filter condition.  Is this a selectivity
> estimation bug?

Doesn't look like it: estimated number of matches is 253635, actual is
259828, which is really astonishingly close considering what we have to
work with.  It's not clear though what fraction of the total that
represents.

            regards, tom lane

pgsql-performance by date:

Previous
From: Robert Haas
Date:
Subject: Re: Full text search with ORDER BY performance issue
Next
From: PFC
Date:
Subject: Re: Full text search with ORDER BY performance issue