Re: Re: 500rows = 1min/2.5k rows=20min/6K rows 2 hours and still running

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: El-Lotso <el(dot)lotso(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Re: 500rows = 1min/2.5k rows=20min/6K rows 2 hours and still running
Date: 2007-09-12 14:41:16
Message-ID: 22159.1189608076@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

El-Lotso <el(dot)lotso(at)gmail(dot)com> writes:
> I'm really at my wits end here.

Try to merge the multiple join keys into one, somehow. I'm not sure why
the planner is overestimating the selectivity of the combined join
conditions, but that's basically where your problem is coming from.

A truly brute-force solution would be "set enable_nestloop = off"
but this is likely to screw performance for other queries.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Rafael Barrera Oro 2007-09-12 18:01:07 Re: random_page_costs - are defaults of 4.0 realistic for SCSI RAID 1
Previous Message Nis Jørgensen 2007-09-12 13:14:25 Re: 500rows = 1min/2.5k rows=20min/6K rows 2 hours and still running