Date: Mon, 29 Sep 2003 13:53:13 -0700 (PDT)
From: Stephan Szabo <sszabo@megazone.bigpanda.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>,
	Bruce Momjian <pgman@candle.pha.pa.us>,
	Peter Childs <Blue.Dragon@blueyonder.co.uk>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta) 
In-Reply-To: <6950.1064868208@sss.pgh.pa.us>
Message-ID: <20030929134904.L97764@megazone.bigpanda.com>
References: <20030815073837.R19338-100000@megazone.bigpanda.com>
	<1718.1064705858@sss.pgh.pa.us>
	<20030928111850.B73144@megazone.bigpanda.com>
	<10377.1064775363@sss.pgh.pa.us>
	<20030929112706.U94710@megazone.bigpanda.com>
	<6950.1064868208@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 29 Sep 2003, Tom Lane wrote:

> Stephan Szabo <sszabo@megazone.bigpanda.com> writes:
> > As an update, so far I still am getting better results with NOT EXISTS
> > than the left join.
>
> Hm.  Don't suppose you were using EXPLAIN ANALYZE so we could see what's
> happening?  This is clearly a planner failure, although I'm unsure if we
> can expect the planner to get the right answer with no pg_statistic entries.

For the sort+seq one and the not exists, I had, but I'll re-run it (it's
on my home desktop that I won't be able to access).  The other when I
forced it to use an index scan I haven't let complete yet, and I don't
know how long that will take.

I was also planning to run a set after running analyze, so I'll include
those too.  It'll probably be a few hours before the results are in. :)

Are there any other options (enable_mergejoin, etc) that you want me to
try with?