| From: | Matthew Wakeling <matthew(at)flymine(dot)org> |
|---|---|
| To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: merge join killing performance |
| Date: | 2010-05-19 03:00:18 |
| Message-ID: | alpine.DEB.2.00.1005182254110.1867@aragorn.flymine.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
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?
Matthew
--
As you approach the airport, you see a sign saying "Beware - low
flying airplanes". There's not a lot you can do about that. Take
your hat off? -- Michael Flanders
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2010-05-19 03:06:25 | Re: merge join killing performance |
| Previous Message | Fujii Masao | 2010-05-19 02:40:19 | Re: Stefan's bug (was: max_standby_delay considered harmful) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2010-05-19 03:06:25 | Re: merge join killing performance |
| Previous Message | Scott Marlowe | 2010-05-19 00:17:33 | merge join killing performance |