From: Josh Berkus <josh@agliodbs.com>
To: Alfranio Junior <alfranio@lsd.di.uminho.pt>
To: pgsql-performance@postgresql.org
Subject: Re: PERFORMANCE and SIZE
Date: Tue, 13 May 2003 09:15:34 -0700
Message-ID: <200305130915.34850.josh@agliodbs.com> (raw)
In-Reply-To: <012a01c3198e$48957270$9002a8c0@ialfranio>
References: <011d01c318be$997217f0$9002a8c0@ialfranio>
<200305120849.39381.josh@agliodbs.com>
<012a01c3198e$48957270$9002a8c0@ialfranio>
Alfranio,
> And now, the optimizer started to use a table scan and in consequence gives
> me:
What appears to me to be happening is that the planner has incorrect estimates
of the cost of an index lookup. The base estimate is contained in the
postgresql.conf parameter:
cpu_index_tuple_cost = 0.001
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com, alfranio@lsd.di.uminho.pt
Subject: Re: PERFORMANCE and SIZE
In-Reply-To: <200305130915.34850.josh@agliodbs.com>
References: <011d01c318be$997217f0$9002a8c0@ialfranio> <200305120849.39381.josh@agliodbs.com> <012a01c3198e$48957270$9002a8c0@ialfranio> <200305130915.34850.josh@agliodbs.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