Received: from bast.unixathome.org (bast.unixathome.org [216.187.105.150]) by postgresql.org (Postfix) with ESMTP id 85314477250 for ; Sat, 16 Mar 2002 17:22:56 -0500 (EST) Received: from wocker (wocker.unixathome.org [192.168.0.99]) by bast.unixathome.org (Postfix) with ESMTP id 15B653F28; Sat, 16 Mar 2002 17:22:58 -0500 (EST) From: "Dan Langille" Organization: DVL Software Limited To: Tom Lane Date: Sat, 16 Mar 2002 17:22:55 -0500 MIME-Version: 1.0 Subject: Re: why the big difference on this explain analyze? Reply-To: dan@langille.org Cc: pgsql-sql References: <20020316220751.A5EE73F28@bast.unixathome.org> In-reply-to: <15913.1016317172@sss.pgh.pa.us> X-mailer: Pegasus Mail for Windows (v4.01) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Message-Id: <20020316222258.15B653F28@bast.unixathome.org> X-Archive-Number: 200203/217 X-Sequence-Number: 7096 On 16 Mar 2002 at 17:19, Tom Lane wrote: > "Dan Langille" writes: > > The difference between the two SQL statements is the inclusion of > > Ports_Check in the WHERE EXISTS select clause. > > Which caused it to do the wrong thing. I think you'll find this > command set found_in_ports = TRUE in *every* row of Ports_Check. Yes, it did. Not quite what I want either.... > Reason: the EXISTS clause no longer depends on the outer update, > but evaluates to a constant TRUE. (Or possibly a constant FALSE, > but that seems unlikely.) Seems I'll have to keep searching for my speed improvement. Thanks for pointing out that problem. cheers. -- Dan Langille The FreeBSD Diary - http://freebsddiary.org/ - practical examples