From: Tom Lane <tgl@sss.pgh.pa.us>
To: Greg Stark <gsstark@mit.edu>
Cc: Richard Huxton <dev@archonet.com>
Cc: David Brown <time@bigpond.net.au>
Cc: pgsql-performance@postgresql.org
Subject: Re: Seqscan rather than Index
Date: Fri, 17 Dec 2004 13:36:52 -0500
Message-ID: <21610.1103308612@sss.pgh.pa.us> (raw)
In-Reply-To: <87zn0cixzy.fsf@stark.xeocode.com>
References: <20041217011853.9E8FF3CADB0@svr1.postgresql.org>
<41C2D936.3060901@archonet.com>
<87acsdkjte.fsf@stark.xeocode.com>
<21110.1103305481@sss.pgh.pa.us>
<87zn0cixzy.fsf@stark.xeocode.com>
Greg Stark <gsstark@mit.edu> writes:
> Tom Lane <tgl@sss.pgh.pa.us> writes:
>> I think the one effect that's not being modeled is amortization of index
>> fetches across successive queries.
> And across multiple fetches in a single query, such as with a nested loop.
Right, that's effectively the same problem. You could imagine making a
special-purpose solution for nestloop queries but I think the issue is
more general than that.
> It seems like the effective_cache_size parameter should be having some
> influence here.
But it doesn't :-(. e_c_s is currently only used to estimate
amortization of repeated heap-page fetches within a single indexscan.
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, gsstark@mit.edu, dev@archonet.com, time@bigpond.net.au
Subject: Re: Seqscan rather than Index
In-Reply-To: <21610.1103308612@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