From: Ed L. <pgsql@bluepolka.net>
To: Kevin Brown <kevin@sysexperts.com>
To: Postgres Performance <pgsql-performance@postgresql.org>
Subject: Re: Column correlation drifts, index ignored again
Date: Tue, 24 Feb 2004 13:54:15 -0700
Message-ID: <200402241354.15025.pgsql@bluepolka.net> (raw)
In-Reply-To: <20040224201419.GD3090@filer>
References: <BC5E98B7.2DCB2%siracusa@mindspring.com>
<23533.1077647386@sss.pgh.pa.us>
<20040224201419.GD3090@filer>
On Tuesday February 24 2004 1:14, Kevin Brown wrote:
>
> 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? Spilling to disk like that will suddenly cause sequential
> reads to perform much more like random reads, unless the sequential
> scans are performed in their entirety between sorts/merges.
How do you know the merge join is spilling to disk? How are you identifying
that? Just assuming from vmstat? iostat?
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: pgsql@bluepolka.net, kevin@sysexperts.com
Subject: Re: Column correlation drifts, index ignored again
In-Reply-To: <200402241354.15025.pgsql@bluepolka.net>
* 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