From: Tom Lane <tgl@sss.pgh.pa.us>
To: siracusa@mindspring.com
Cc: pgsql-performance@postgresql.org
Subject: Re: Use my (date) index, darn it!
Date: Mon, 05 Jan 2004 01:55:43 -0500
Message-ID: <22764.1073285743@sss.pgh.pa.us> (raw)
In-Reply-To: <BC1E0DA0.219D2%siracusa@mindspring.com>
References: <BC1E0DA0.219D2%siracusa@mindspring.com>
John Siracusa <siracusa@mindspring.com> writes:
> Obviously the planner is making some bad choices here.
A fair conclusion ...
> I know that it is trying to avoid random seeks or other scary things
> implied by a "correlation" statistic that is not close to 1 or -1, but
> it is massively overestimating the hit caused by those seeks and
> seemingly not taking into account the size of the table!
You haven't given any evidence to support these conclusions, though.
Could we see some table schemas, EXPLAIN ANALYZE output, and relevant
pg_stats entries for the various cases?
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-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, siracusa@mindspring.com
Subject: Re: Use my (date) index, darn it!
In-Reply-To: <22764.1073285743@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