From: Tom Lane <tgl@sss.pgh.pa.us>
To: rigmor.ukuhe@finestmedia.com
Cc: Matt Clark <matt@ymogen.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Index problem
Date: Thu, 25 Sep 2003 09:38:27 -0400
Message-ID: <2395.1064497107@sss.pgh.pa.us> (raw)
In-Reply-To: <OEEHLFAIJHHMABJPIANIMEMICFAA.rigmor.ukuhe@finestmedia.com>
References: <OEEHLFAIJHHMABJPIANIMEMICFAA.rigmor.ukuhe@finestmedia.com>
"Rigmor Ukuhe" <rigmor.ukuhe@finestmedia.com> writes:
>>> What causes this behaviour? is there any workaround? Suggestions?
At some point the planner is going to decide that one seqscan is cheaper
than repeated indexscans. At some point it'll be right ... but in this
case it seems its relative cost estimates are off a bit. You might try
reducing random_page_cost to bring them more into line with reality.
(But keep in mind that the reality you are measuring appears to be
small-table-already-fully-cached reality. On a large table you might
find that small random_page_cost isn't such a hot idea after all.)
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, rigmor.ukuhe@finestmedia.com, matt@ymogen.net
Subject: Re: Index problem
In-Reply-To: <2395.1064497107@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