From: Greg Stark <gsstark@mit.edu>
To: Scott Marlowe <smarlowe@qwest.net>
Cc: Jack Kerkhof <jack.kerkhof@guest-tek.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Why does a simple query not use an obvious index?
Date: 29 Aug 2004 17:12:05 -0400
Message-ID: <87fz65k5sq.fsf@stark.xeocode.com> (raw)
In-Reply-To: <1093804128.5493.22.camel@localhost.localdomain>
References: <ENEIKKAEJOFHOIHMMOIDIEBMJCAA.jack.kerkhof@guest-tek.com>
<1093804128.5493.22.camel@localhost.localdomain>
"Scott Marlowe" <smarlowe@qwest.net> writes:
> 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:
Huh? I'm curious to know what you're talking about here.
> select somefield from sometable where timestampfield > now()-'60
> seconds'::interval
>
> and count the number of returned rows. If there's a lot, it won't be
> any faster, if there's a few, it should be a win.
Why would this ever be faster? And how could postgres ever calculate that
without doing a sequential scan when count(*) would force it to do a
sequential scan?
--
greg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: gsstark@mit.edu, smarlowe@qwest.net, jack.kerkhof@guest-tek.com
Subject: Re: Why does a simple query not use an obvious index?
In-Reply-To: <87fz65k5sq.fsf@stark.xeocode.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox