From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kelly Burkhart <kelly@tradebotsystems.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: optimizer tuning/forcing correct index use
Date: Tue, 19 Mar 2002 10:28:42 -0500
Message-ID: <29145.1016551722@sss.pgh.pa.us> (raw)
In-Reply-To: <02031907224907.00735@krbdev>
References: <02031907224907.00735@krbdev>
Kelly Burkhart <kelly@tradebotsystems.com> writes:
> The critical part is driving the fill table query from a sequential scan
> rather than a scan of fill_ak2.
Have you done an ANALYZE or VACUUM ANALYZE lately? If so, what do you
get from
select * from pg_stats where tablename = 'fill';
select * from pg_class where relname = 'fill';
Offhand I am guessing that the table is fairly well ordered by fill_ts
and the planner is underestimating the effects of this. There is a
provision in there to try to account for data ordering, but it's new
code in 7.2 and doubtless still needs refinement.
regards, tom lane
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: tgl@sss.pgh.pa.us, kelly@tradebotsystems.com
Subject: Re: optimizer tuning/forcing correct index use
In-Reply-To: <29145.1016551722@sss.pgh.pa.us>
* 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