From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jim C. Nasby <jnasby@pervasive.com>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Blocks read for index scans
Date: Fri, 14 Apr 2006 11:12:55 -0400
Message-ID: <9369.1145027575@sss.pgh.pa.us> (raw)
In-Reply-To: <20060414061414.GY49405@pervasive.com>
References: <85979594-1CCA-43C5-A8F2-08685CF41ACE@pervasive.com>
<2789.1144974969@sss.pgh.pa.us>
<20060414061414.GY49405@pervasive.com>
"Jim C. Nasby" <jnasby@pervasive.com> writes:
> In my case it would be helpful to break the heap access numbers out
> between seqscans and index scans, since each of those represents very
> different access patterns. Would adding that be a mess?
Yes; it'd require more counters-per-table than we now keep, thus
nontrivial bloat in the stats collector's tables. Not to mention
incompatible changes in the pgstats views and the underlying functions
(which some apps probably use directly).
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, jnasby@pervasive.com
Subject: Re: Blocks read for index scans
In-Reply-To: <9369.1145027575@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