Re: Bad plan for nested loop + limit - Mailing list pgsql-performance

From David Wilson
Subject Re: Bad plan for nested loop + limit
Date
Msg-id e7f9235d0902142029h5b53baf2gede92b22afbbad35@mail.gmail.com
Whole thread Raw
In response to Bad plan for nested loop + limit  (Alexander Staubo <alex@bengler.no>)
Responses Re: Bad plan for nested loop + limit  (Alexander Staubo <alex@bengler.no>)
List pgsql-performance
On Sat, Feb 14, 2009 at 5:25 PM, Alexander Staubo <alex@bengler.no> wrote:
>
> Output from "explain analyze":
>
>  Limit  (cost=0.00..973.63 rows=4 width=48) (actual
> time=61.554..4039.704 rows=1 loops=1)
>   ->  Nested Loop  (cost=0.00..70101.65 rows=288 width=48) (actual
> time=61.552..4039.700 rows=1 loops=1)
>         ->  Nested Loop  (cost=0.00..68247.77 rows=297 width=52)
> (actual time=61.535..4039.682 rows=1 loops=1)

Those estimates are pretty far off. Did you try increasing the
statistics target? Also, is the first query repeatable (that is, is it
already in cache when you do the test, or alternately, are all queries
*out* of cache when you test?)
--
- David T. Wilson
david.t.wilson@gmail.com

pgsql-performance by date:

Previous
From: Alexander Staubo
Date:
Subject: Bad plan for nested loop + limit
Next
From: Alexander Staubo
Date:
Subject: Re: Bad plan for nested loop + limit