X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 88F91D1B450 for ; Thu, 25 Dec 2003 16:29:50 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 96122-06 for ; Thu, 25 Dec 2003 12:29:01 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 4A210D1B455 for ; Thu, 25 Dec 2003 12:29:00 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id hBPGSs19020566; Thu, 25 Dec 2003 11:28:54 -0500 (EST) To: "Michael Rothschild" Cc: pgsql-performance@postgresql.org Subject: Re: In-reply-to: References: Comments: In-reply-to "Michael Rothschild" message dated "Wed, 24 Dec 2003 18:25:43 +0200" Date: Thu, 25 Dec 2003 11:28:54 -0500 Message-ID: <20565.1072369734@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/297 X-Sequence-Number: 5157 "Michael Rothschild" writes: > Based on what I saw (and maybe I didn't see enough) it seems that the > optimizer will always decide to repeatedly scan the whole row set > returned by sub selects in the context of an IN clause sequentially, What version were you looking at? regards, tom lane