From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kevin Brown <kevin@sysexperts.com>
Cc: Postgres Performance <pgsql-performance@postgresql.org>
Subject: Re: Column correlation drifts, index ignored again
Date: Tue, 24 Feb 2004 17:16:08 -0500
Message-ID: <27171.1077660968@sss.pgh.pa.us> (raw)
In-Reply-To: <20040224201419.GD3090@filer>
References: <BC5E98B7.2DCB2%siracusa@mindspring.com>
<200402221617.27658.josh@agliodbs.com>
<20040224035601.GC3090@filer>
<200402240859.32312.josh@agliodbs.com>
<23533.1077647386@sss.pgh.pa.us>
<20040224201419.GD3090@filer>
Kevin Brown <kevin@sysexperts.com> writes:
> One problem I've been running into is the merge join spilling to disk
> because sort_mem isn't big enough. The problem isn't that this is
> happening, it's that I think the planner is underestimating the impact
> that doing this will have on the time the merge join takes. Does the
> planner even account for the possibility that a sort or join will spill
> to disk?
Yes it does. I thought it was making a pretty good estimate, actually.
The only obvious hole in the assumptions is
* The disk traffic is assumed to be half sequential and half random
* accesses (XXX can't we refine that guess?)
Because of the way that tuplesort.c works, the first merge pass should
be pretty well sequential, but I think the passes after that might be
mostly random from the kernel's viewpoint :-(. Possibly the I/O cost
should be adjusted depending on how many merge passes we expect.
> In any case, one thing that none of this really accounts for is that
> it's better to set random_page_cost too low than too high.
That depends on what you are doing, although I will concede that a lot
of people are doing things where indexscans should be favored.
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, kevin@sysexperts.com
Subject: Re: Column correlation drifts, index ignored again
In-Reply-To: <27171.1077660968@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