On Tue, May 18, 2010 at 9:00 PM, Matthew Wakeling <matthew@xxxxxxxxxxx> wrote: > On Tue, 18 May 2010, Scott Marlowe wrote: >> >> Aggregate (cost=902.41..902.42 rows=1 width=4) >> -> Merge Join (cost=869.97..902.40 rows=1 width=4) >> Merge Cond: (f.eid = ev.eid) >> -> Index Scan using files_eid_idx on files f >> (cost=0.00..157830.39 rows=3769434 width=8) > > Okay, that's weird. How is the cost of the merge join only 902, when the > cost of one of the branches 157830, when there is no LIMIT? > > Are the statistics up to date? Yep. The explain analyze shows it being close enough it should guess right (I think) We have default stats target set to 200 and the table is regularly analyzed by autovac, which now has much smaller settings for threshold and % than default to handle these big tables. -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
