"Virag Saksena" <virag(at)auptyma(dot)com> writes:
> The individual queries run in 50-300 ms. However the optimizer is =
> choosing a nested loop to join them rather than a Hash join
> causing the complete query to take 500+ seconds. It expects that it will =
> get 1 row out from each of the sources, but here is gets
> several thousand rows.
The best approach is to see if you can't fix that estimation error.
Are the stats up to date on these tables? If so, maybe raising the
statistics targets would help.
regards, tom lane
In response to
pgsql-performance by date
|Next:||From: Craig A. James||Date: 2006-02-21 05:54:14|
|Subject: Re: Cost Issue - How do I force a Hash Join|
|Previous:||From: Virag Saksena||Date: 2006-02-21 05:13:34|
|Subject: Cost Issue - How do I force a Hash Join|