Received: from mail.toppoint.de (LaForge.toppoint.de [195.244.243.6]) by hub.org (8.9.3/8.9.3) with SMTP id VAA62217 for ; Fri, 12 Nov 1999 21:33:05 -0500 (EST) (envelope-from feki.toppoint.de!marten@toppoint.de) Received: by mail.toppoint.de (Smail3.1.29.1) id ; Sat, 13 Nov 99 03:33 MET Received: (from marten@localhost) by feki.phoenix-edv.netzservice.de (8.9.3/8.9.3) id IAA05096; Fri, 12 Nov 1999 08:42:26 +0100 From: marten@feki.toppoint.de Message-Id: <199911120742.IAA05096@feki.phoenix-edv.netzservice.de> Subject: Re: [SQL] Nested Views take forever In-Reply-To: <21836.942366846@sss.pgh.pa.us> from Tom Lane at "Nov 11, 1999 7:34: 6 pm" To: tgl@sss.pgh.pa.us (Tom Lane) Date: Fri, 12 Nov 1999 08:42:26 +0100 (CET) Cc: zot@zotconsulting.com, pgsql-sql@hub.org X-Mailer: ELM [version 2.4ME+ PL47 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > > There's been some talk of reimplementing WHERE ... IN ... so that it > does something intelligent without help, but there are a lot of > higher-priority problems on the TODO list... > > regards, tom lane This only affect statement, where the "inner" select accesses some stuff of the "outer" select statement ? Actually a statement like: select * from table where index in (select foreign-key from table2 where table2.name = 'Hallo') would not have such problems ? Correct ? Marten