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 C3FB4D1B45B for ; Fri, 30 Jan 2004 14:51:10 +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 53907-09 for ; Fri, 30 Jan 2004 10:51:14 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id BCBD8D1B45A for ; Fri, 30 Jan 2004 10:51:09 -0400 (AST) 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 i0UEpAMa013027; Fri, 30 Jan 2004 09:51:11 -0500 (EST) To: Dennis Bjorklund Cc: Jack Coates , pgsql-performance Subject: Re: query optimization question In-reply-to: References: Comments: In-reply-to Dennis Bjorklund message dated "Fri, 30 Jan 2004 08:19:43 +0100" Date: Fri, 30 Jan 2004 09:51:10 -0500 Message-ID: <13026.1075474270@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/325 X-Sequence-Number: 5499 Dennis Bjorklund writes: > Getting rid of the group by would not give that kind of speedup? No. Getting rid of the per-row subqueries (or at least finding a way to make 'em a lot cheaper) is the only way to make any meaningful change. regards, tom lane