From: Jeroen van Iddekinge <iddekingej@lycos.com>
To: pgsql-performance@postgresql.org
Subject: Re: sequence scan on PK
Date: Sun, 08 May 2005 17:49:36 +0000
Message-ID: <427E5130.7020702@lycos.com> (raw)
In-Reply-To: <427E17BC.7050407@arbash-meinel.com>
References: <427E2941.9070105@lycos.com>
<427E17BC.7050407@arbash-meinel.com>
>
> You could tweak with several settings to get it to do an index scan
> earlier, but these would probably break other queries. You don't need to
> tune for 100 rows, morelike 100k or 100M.
Thanks for respone.
The index scan was a little bit faster for id=1 and faster for id=99.
Which settings shoud I change for this? cpu_index_tuple_cost ,
cpu_operator_cost, cpu_tuple_cost?
Jer.
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: iddekingej@lycos.com
Subject: Re: sequence scan on PK
In-Reply-To: <427E5130.7020702@lycos.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