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 4903FD1B433 for ; Mon, 5 Jan 2004 20:01:57 +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 49271-05 for ; Mon, 5 Jan 2004 16:01:08 -0400 (AST) Received: from cayenne.palmdigitalmedia.com (cayenne.palmdigitalmedia.com [63.110.43.230]) by svr1.postgresql.org (Postfix) with SMTP id 55634D1B444 for ; Mon, 5 Jan 2004 16:01:06 -0400 (AST) Received: (qmail 21093 invoked from network); 5 Jan 2004 20:01:07 -0000 Received: from unknown (HELO ?192.168.124.23?) (63.110.43.226) by 0 with SMTP; 5 Jan 2004 20:01:07 -0000 User-Agent: Microsoft-Entourage/10.1.1.2418 Date: Mon, 05 Jan 2004 15:01:18 -0500 Subject: Re: Select max(foo) and select count(*) optimization From: John Siracusa To: Postgres Performance Message-ID: In-Reply-To: <1073332325.8958.8.camel@jester> Mime-version: 1.0 Reply-To: siracusa@mindspring.com Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/51 X-Sequence-Number: 5226 On 1/5/04 2:52 PM, Rod Taylor wrote: > max(foo) optimizations requires an extension to the aggregates system. > It will likely happen within a few releases. Looking forward to it. > A work around can be accomplished today through the use of LIMIT and ORDER BY. Wowzers, I never imagined that that'd be so much faster. Thanks! :) -John