X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 3E925D1B1B3 for ; Sat, 29 May 2004 02:06:33 -0300 (ADT) 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 78037-08 for ; Sat, 29 May 2004 02:06:31 -0300 (ADT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 024F9D1B16F for ; Sat, 29 May 2004 02:06:30 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i4T566iH015005; Sat, 29 May 2004 01:06:06 -0400 (EDT) To: Josh Sacks Cc: pgsql-performance@postgresql.org Subject: Re: Not using Primary Key in query In-reply-to: References: Comments: In-reply-to Josh Sacks message dated "Tue, 25 May 2004 11:37:55 -0700" Date: Sat, 29 May 2004 01:06:05 -0400 Message-ID: <15004.1085807165@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200405/224 X-Sequence-Number: 7055 Josh Sacks writes: > I can't understand what's going on in this simple query: If you are using anything older than PG 7.4, you should not expect good performance from WHERE ... IN (sub-SELECT) queries. There's essentially no optimization happening there. regards, tom lane