X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 744A45E3F15 for ; Mon, 30 Aug 2004 16:19:45 -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 05319-10 for ; Mon, 30 Aug 2004 19:19:40 +0000 (GMT) Received: from boutiquenumerique.com (gailleton-2-82-67-9-10.fbx.proxad.net [82.67.9.10]) by svr1.postgresql.org (Postfix) with ESMTP id 5DB365E46F8 for ; Mon, 30 Aug 2004 16:19:40 -0300 (ADT) Received: (qmail 27663 invoked from network); 30 Aug 2004 21:19:54 +0200 Received: from unknown (HELO musicbox) (192.168.0.2) by gailleton-2-82-67-9-10.fbx.proxad.net with SMTP; 30 Aug 2004 21:19:54 +0200 To: pgsql-performance@postgresql.org Subject: Re: Why does a simple query not use an obvious index? References: <1093804128.5493.22.camel@localhost.localdomain> <87fz65k5sq.fsf@stark.xeocode.com> Message-ID: Date: Mon, 30 Aug 2004 21:21:26 +0200 From: =?iso-8859-15?Q?Pierre-Fr=E9d=E9ric_Caillaud?= Organization: =?iso-8859-15?Q?La_Boutique_Num=E9rique?= Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: <87fz65k5sq.fsf@stark.xeocode.com> User-Agent: Opera M2/7.53 (Linux, build 737) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/453 X-Sequence-Number: 8089 >> Also, count(*) is likely to always generate a seq scan due to the way >> aggregates are implemented currently in pgsql. you might want to try: By the way, in an ideal world, count(*) should only read the index on the timetamp column, not the rows. I guess this is not the case. Would this be an useful optimization ?