From: Jim C. Nasby <decibel@decibel.org>
To: Tobias Brox <tobias@nordicbet.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: timestamp indexing
Date: Thu, 9 Jun 2005 13:04:53 -0500
Message-ID: <20050609180453.GQ44623@decibel.org> (raw)
In-Reply-To: <20050531022011.GC26100@tobias.exoweb.net>
References: <20050530091951.GO26100@tobias.exoweb.net>
<20050530135429.GA78082@winnie.fuhr.org>
<20050530170816.GA9222@oppetid.no>
<24839.1117475874@sss.pgh.pa.us>
<20050531020625.GA26100@tobias.exoweb.net>
<20050531022011.GC26100@tobias.exoweb.net>
What does
SET enable_seqscan = false;
EXPLAIN ANALYZE SELECT * FROM ...
get you? Is it faster?
BTW, I suspect this behavior is because the estimates for the cost of an
index scan don't give an appropriate weight to the correlation of the
index. The 'sort and index' thread on this list from a few months ago
has more info.
--
Jim C. Nasby, Database Consultant decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
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: decibel@decibel.org, tobias@nordicbet.com
Subject: Re: timestamp indexing
In-Reply-To: <20050609180453.GQ44623@decibel.org>
* 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