Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
	by hub.org (8.9.3/8.9.3) with ESMTP id KAA49915
	for <pgsql-interfaces@postgreSQL.org>;
	Thu, 2 Dec 1999 10:49:28 -0500 (EST)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id KAA27910;
	Thu, 2 Dec 1999 10:21:44 -0500 (EST)
To: dougt@mugc.cc.monash.edu.au
cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Slow join query optimisation? 
In-reply-to: Your message of Thu, 2 Dec 1999 14:25:52 +1100 (EST)
	<199912020325.OAA13610@mugca.cc.monash.edu.au>
Date: Thu, 02 Dec 1999 10:21:43 -0500
Message-ID: <27908.944148103@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Douglas Thomson <dougt@mugc.cc.monash.edu.au> writes:
> Is there any way to turn off the optimisation? Or perhaps some way to
> work out the optimal strategy once, and then provide this information
> directly?

Not at the moment.  There's been some talk of caching query plans,
which would get the job done, but none of the current developers are
working on that now.  It'll probably happen someday...

			regards, tom lane