From: | Jasmin Dizdarevic <jasmin(dot)dizdarevic(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Performance of NOT IN and <> with PG 9.0.4 |
Date: | 2011-05-25 15:23:12 |
Message-ID: | BANLkTikRhu7NYb9FdorgMP9hrXW6p+Z-Lw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
As I've understood the docs those 2 limits should not take effect, because
the performance is going down when adding two aggregated columns, but only
when enable_material is on.
2011/5/25 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > On Tue, May 24, 2011 at 3:32 PM, Jasmin Dizdarevic
> > <jasmin(dot)dizdarevic(at)gmail(dot)com> wrote:
> >> enable_material = off
>
> > Is there any chance you can reproduce this with a simpler test case
> > that doesn't involve quite so many joins?
>
> I didn't stop to count, but are there enough that join_collapse_limit
> or from_collapse_limit could be in play?
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Rob Sargent | 2011-05-25 15:25:48 | Re: extracting location info from string |
Previous Message | Tom Lane | 2011-05-25 14:13:21 | Re: Performance of NOT IN and <> with PG 9.0.4 |