From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jim C. Nasby <decibel@decibel.org>
Cc: John Meinel <john@johnmeinel.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Sequential Scan with LIMIT
Date: Thu, 28 Oct 2004 19:49:28 -0400
Message-ID: <9172.1099007368@sss.pgh.pa.us> (raw)
In-Reply-To: <20041028234658.GI55164@decibel.org>
References: <417C023F.1080502@johnmeinel.com>
<17689.1098648713@sss.pgh.pa.us>
<20041028234658.GI55164@decibel.org>
"Jim C. Nasby" <decibel@decibel.org> writes:
> On Sun, Oct 24, 2004 at 04:11:53PM -0400, Tom Lane wrote:
>> The test case you are showing is probably suffering from nonrandom
>> placement of this particular data value; which is something that the
>> statistics we keep are too crude to detect.
> Isn't that exactly what pg_stats.correlation is?
No. A far-from-zero correlation gives you a clue that on average, *all*
the data values are placed nonrandomly ... but it doesn't really tell
you much one way or the other about a single data value.
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, decibel@decibel.org, john@johnmeinel.com
Subject: Re: Sequential Scan with LIMIT
In-Reply-To: <9172.1099007368@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