Re: Improving join performance over multiple moderately wide tables

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: miller_2555 <nabble(dot)30(dot)miller_2555(at)spamgourmet(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Improving join performance over multiple moderately wide tables
Date: 2009-10-19 00:49:42
Message-ID: 603c8f070910181749m200a0ff5kcc967f016cd9bad7@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Fri, Oct 16, 2009 at 5:12 PM, miller_2555
<nabble(dot)30(dot)miller_2555(at)spamgourmet(dot)com> wrote:
>  [...snip...] attempted to set the `join_collapse_limit` to '1' [...]

That seems like an odd thing to do - why did you do this? What
happens if you don't?

I have never seen anything like the bizarrely large row estimates that
you have here. Any chance you can extract a standalone, reproducible
test case?

...Robert

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Robert Haas 2009-10-19 00:52:34 Re: Performance with sorting and LIMIT on partitioned table
Previous Message Tom Lane 2009-10-18 23:41:38 Re: Calculation of unused columns