From: | Mark Lubratt <mark(dot)lubratt(at)indeq(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org, josh(at)agliodbs(dot)com |
Subject: | Re: tsearch query plan |
Date: | 2004-04-09 03:28:37 |
Message-ID: | FD09DC53-89D5-11D8-80A0-000A9579AF50@indeq.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Apr 8, 2004, at 6:33 PM, Josh Berkus wrote:
> Mark,
>
>> 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"?
>
> Well, your example is not "a couple orders of magnitude". 6 vs. 32 is
> actually pretty good accuracy.
>
> Now, 6 vs 192 would potentially be a problem, let alone 32 vs 13,471.
>
I guess I was looking more at the cost estimate and not so much at the
rows estimate. I agree that the row estimate wasn't too bad. But the
cost estimate seems way out of line.
I'm somewhat new to examining explain analyze output and I'm looking at
this as more of an education, since the speed is certainly good anyway.
I just expected the cost estimate to be more in line especially
immediately after an analyze.
-Mark
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-04-09 05:26:51 | Re: tsearch query plan |
Previous Message | Josh Berkus | 2004-04-08 23:33:40 | Re: tsearch query plan |