X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 86248529B2 for ; Wed, 10 Aug 2005 00:29:44 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 33138-04 for ; Wed, 10 Aug 2005 03:29:42 +0000 (GMT) Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by svr1.postgresql.org (Postfix) with ESMTP id 1824A529AD for ; Wed, 10 Aug 2005 00:29:41 -0300 (ADT) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.3/8.13.3) with ESMTP id j7A3TD4F045777 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 9 Aug 2005 21:29:16 -0600 (MDT) (envelope-from mfuhr@winnie.fuhr.org) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.3/8.13.3) with ESMTP id j7A3TDgW040990; Tue, 9 Aug 2005 21:29:13 -0600 (MDT) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.3/8.13.3/Submit) id j7A3TDQ5040989; Tue, 9 Aug 2005 21:29:13 -0600 (MDT) (envelope-from mfuhr) Date: Tue, 9 Aug 2005 21:29:13 -0600 From: Michael Fuhr To: Tom Lane Cc: dracula007@atlas.cz, pgsql-sql@postgresql.org Subject: Re: **SPAM** Faster count(*)? Message-ID: <20050810032913.GA40917@winnie.fuhr.org> References: <000101c59d33$36a4a560$9b00015a@osl.com> <196456155.20050810012958@karneval.cz> <21626.1123642154@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <21626.1123642154@sss.pgh.pa.us> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.005 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200508/45 X-Sequence-Number: 22273 On Tue, Aug 09, 2005 at 10:49:14PM -0400, Tom Lane wrote: > Current best practice is to run the explain and parse out the "rows" > figure using a perl (or axe-of-choice) regexp, though we could be > persuaded to supply a simpler API if there's enough demand for it. Somebody else requested a row-count-estimate function a couple of weeks ago: http://archives.postgresql.org/pgsql-admin/2005-07/msg00256.php -- Michael Fuhr