From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeroen van Iddekinge <iddekingej@lycos.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: sequence scan on PK
Date: Sun, 08 May 2005 12:49:19 -0400
Message-ID: <12303.1115570959@sss.pgh.pa.us> (raw)
In-Reply-To: <427E5130.7020702@lycos.com>
References: <427E2941.9070105@lycos.com>
<427E17BC.7050407@arbash-meinel.com>
<427E5130.7020702@lycos.com>
Jeroen van Iddekinge <iddekingej@lycos.com> writes:
>> 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.
> Which settings shoud I change for this?
I'd agree with John's response: if you change any settings based on just
this one test case, you're a fool. But usually random_page_cost is the
best knob to twiddle if you wish to encourage indexscans.
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, iddekingej@lycos.com
Subject: Re: sequence scan on PK
In-Reply-To: <12303.1115570959@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