From: Mark Kirkwood <markir@paradise.net.nz>
To: Jim C. Nasby <jnasby@pervasive.com>
Cc: Terje Elde <terje@elde.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Blocks read for index scans
Date: Wed, 19 Apr 2006 17:31:21 +1200
Message-ID: <4445CB29.1010605@paradise.net.nz> (raw)
In-Reply-To: <20060419051346.GQ49405@pervasive.com>
References: <85979594-1CCA-43C5-A8F2-08685CF41ACE@pervasive.com>
<443F3BB3.30404@elde.net>
<20060418200641.GG49405@pervasive.com>
<4445A1DF.6000705@elde.net>
<20060419051346.GQ49405@pervasive.com>
Jim C. Nasby wrote:
>
> Yeah... not gonna happen...
>
> It's completely mind-boggling that FBSD doesn't track writes and reads
> seperately.
'iostat' does not tell you this, but 'gstat' does - its the "geom"
system monitor (a bit annoying that the standard tool is lacking in this
regard...).
Cheers
Mark
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: markir@paradise.net.nz, jnasby@pervasive.com, terje@elde.net
Subject: Re: Blocks read for index scans
In-Reply-To: <4445CB29.1010605@paradise.net.nz>
* 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