tsearch query plan

From: Mark Lubratt <mark(dot)lubratt(at)indeq(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: tsearch query plan
Date: 2004-04-08 17:33:28
Message-ID: D8C70D62-8982-11D8-90A0-000A9579AF50@indeq.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Hello,

I've just started using the tsearch2 system. I'm VERY impressed by the
speed.

I've got one question about query planning. Is it understandable to
have the query plan estimation be off by a couple of orders of
magnitude? Or, is it the fact that the cost estimation is small to
begin with that the error between the actual and the estimated is
"normal"?

Here is my explain analyze run immediately after a vacuum full analyze:

kjv=# vacuum full analyze;
VACUUM
kjv=# explain analyze select * from kjv where idxFTI @@
'corinth'::tsquery;
QUERY PLAN
------------------------------------------------------------------------
---------------------------------------------
Index Scan using idxfti_idx on kjv (cost=0.00..125.44 rows=32
width=193) (actual time=0.796..1.510 rows=6 loops=1)
Index Cond: (idxfti @@ '\'corinth\''::tsquery)
Filter: (idxfti @@ '\'corinth\''::tsquery)
Total runtime: 1.679 ms
(4 rows)

Thanks!
Mark

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Jaime Casanova 2004-04-08 22:42:25 Re: statistics
Previous Message Robert Treat 2004-04-08 15:06:11 Re: Postgresql educational sources