Csaba Nagy <nagy(at)ecircle-ag(dot)com> writes:
> Looking at Plan 2, it looks like the "limit" step is estimating wrongly
> it's cost.
The reason you get a bad plan is that this rowcount estimate is so far
> -> Index Scan using pk_table_a on table_a ta (cost=0.00..324786.18 rows=388532 width=16) (actual time=454.389..460.138 rows=2 loops=1)
> Index Cond: (a = $1)
Raising the stats target helped no doubt because it didn't overestimate
the number of rows so much...
regards, tom lane
In response to
pgsql-performance by date
|Next:||From: Kevin Grittner||Date: 2007-09-21 16:35:15|
|Subject: Re: query io stats and finding a slow query|
|Previous:||From: Csaba Nagy||Date: 2007-09-21 15:48:09|
|Subject: Re: Searching for the cause of a bad plan|