From: Gerald Gutierrez <gml1@coldresist.com>
To: Koen Antonissen <Koen@Cee-Kay.net>
To: bernd pinter <bernd@uptime.at>
Cc: pgsql-sql@postgresql.org
Subject: RE: primary key scans in sequence
Date: Thu, 31 May 2001 16:26:33 -0700
Message-ID: <5.1.0.14.0.20010531162518.00ae4a68@coldresist.com> (raw)
In-Reply-To: <DD782DD61CF86144BD78DDC89D3D6124017021@gaea.home.dutchcent ral.net>
I think you're just witnessing the optimizer at work. If it thinks that
doing sequential scans is faster, it will ignore the indices.
At 11:03 AM 5/31/2001 +0200, Koen Antonissen wrote:
>Thing I descovered after i posted to the group was that after creating
>the scheme again, the indexes are used! after vacuum (analyze) the use
>of indexes was gone again on certain tables...
>
>Any other suggestions?
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-sql@postgresql.org
Cc: gml1@coldresist.com, Koen@Cee-Kay.net, bernd@uptime.at
Subject: RE: primary key scans in sequence
In-Reply-To: <5.1.0.14.0.20010531162518.00ae4a68@coldresist.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