Re: [PERFORM] 8.2.4 Chooses Bad Query Plan

2007-08-28 Thread Tom Lane
Pallav Kalva <[EMAIL PROTECTED]> writes: > I have analyzed tables again and also my default_stats_target is set to > 100, still it shows the same plan. >>> -> Index Scan using idx_accountactivity_fkactivityid on >>> accountactivity accountact0_ (cost=0.00..3.94 rows=1 width=16) >>> Index Cond: (

Re: [PERFORM] 8.2.4 Chooses Bad Query Plan

2007-08-28 Thread Pallav Kalva
Hi Tom, Thanks! for the reply, see my comments below Tom Lane wrote: > Pallav Kalva <[EMAIL PROTECTED]> writes: > >> We have recently upgraded our production database from 8.0.12 to >> 8.2.4, We have seen lot of improvements on 8.2.4 side but we are also >> seeing some queries which are

Re: [PERFORM] 8.2.4 Chooses Bad Query Plan

2007-08-28 Thread Tom Lane
Pallav Kalva <[EMAIL PROTECTED]> writes: > We have recently upgraded our production database from 8.0.12 to > 8.2.4, We have seen lot of improvements on 8.2.4 side but we are also > seeing some queries which are slow. > Particularly this below query is really bad in 8.2.4 , I can get > onl

[PERFORM] 8.2.4 Chooses Bad Query Plan

2007-08-28 Thread Pallav Kalva
Hi, We have recently upgraded our production database from 8.0.12 to 8.2.4, We have seen lot of improvements on 8.2.4 side but we are also seeing some queries which are slow. Particularly this below query is really bad in 8.2.4 , I can get only the explain on this as explain analyze never