X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id A4FF4D1B8AA for ; Sun, 24 Aug 2003 18:38:31 -0300 (ADT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 69543-07 for ; Sun, 24 Aug 2003 18:38:19 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 81FCBD1BAB3 for ; Sun, 24 Aug 2003 18:38:16 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h7OLcH5H006426; Sun, 24 Aug 2003 17:38:17 -0400 (EDT) To: Mike Winter Cc: pgsql-sql@postgresql.org Subject: Re: "SELECT IN" Still Broken in 7.4b In-reply-to: References: Comments: In-reply-to Mike Winter message dated "Wed, 20 Aug 2003 10:32:45 -0600" Date: Sun, 24 Aug 2003 17:38:16 -0400 Message-ID: <6425.1061761096@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/291 X-Sequence-Number: 14907 Mike Winter writes: > Basically, queries of the form SELECT FROM WHERE IN > () take forever for high numbers of rows in the IN clause. > We've done timing on 7.3 and 7.4b and there is no speed improvement on > these queries. > Does anyone know what the status of this bug is? Try it in CVS tip ... regards, tom lane