From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Brown <time@bigpond.net.au>
Cc: pgsql-performance@postgresql.org
Subject: Re: Planner really hates nested loops
Date: Thu, 03 Feb 2005 11:25:31 -0500
Message-ID: <16694.1107447931@sss.pgh.pa.us> (raw)
In-Reply-To: <420206AD.8040206@bigpond.net.au>
References: <420206AD.8040206@bigpond.net.au>
David Brown <time@bigpond.net.au> writes:
> I'm hoping someone can shed some light on these results.
Not without a lot more detail on how you *got* the results. What
exactly did you do to force the various plan choices? (I see some
ridiculous choices of indexscans, for instance, suggesting improper use
of enable_seqscan in some cases.) And what's the "cache rows" and "disk
rows" stuff, and how do you know that what you were measuring is
actually what you think it is? I have zero confidence in
Windows-atop-ATA as a platform for measuring disk-related behaviors,
because I don't think you can control or even know what caching is
going on.
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, time@bigpond.net.au
Subject: Re: Planner really hates nested loops
In-Reply-To: <16694.1107447931@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