Re: Performance of NOT IN and <> with PG 9.0.4 - Mailing list pgsql-sql

From Jasmin Dizdarevic
Subject Re: Performance of NOT IN and <> with PG 9.0.4
Date
Msg-id BANLkTikRhu7NYb9FdorgMP9hrXW6p+Z-Lw@mail.gmail.com
Whole thread Raw
In response to Re: Performance of NOT IN and <> with PG 9.0.4  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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@sss.pgh.pa.us>
Robert Haas <robertmhaas@gmail.com> writes:
> On Tue, May 24, 2011 at 3:32 PM, Jasmin Dizdarevic
> <jasmin.dizdarevic@gmail.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

pgsql-sql by date:

Previous
From: Rob Sargent
Date:
Subject: Re: extracting location info from string
Next
From: Tarlika Elisabeth Schmitz
Date:
Subject: Re: extracting location info from string