From: Tom Lane <tgl@sss.pgh.pa.us>
To: Curtis Zinzilieta <curtisz@norchemlab.com>
Cc: Anjan Dave <adave@vantage.com>
Cc: Matt Clark <matt@ymogen.net>
Cc: Rod Taylor <pg@rbt.ca>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: can't handle large number of INSERT/UPDATEs
Date: Tue, 26 Oct 2004 23:21:31 -0400
Message-ID: <15812.1098847291@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.44.0410261557560.23730-100000@hyperion2.norchemlab.com>
References: <Pine.LNX.4.44.0410261557560.23730-100000@hyperion2.norchemlab.com>
Curtis Zinzilieta <curtisz@norchemlab.com> writes:
> On Tue, 26 Oct 2004, Tom Lane wrote:
>> Er ... it *is* the other way around. bi is blocks in (to the CPU),
>> bo is blocks out (from the CPU).
> Ummm.....
> [curtisz@labsoft T2]$ man vmstat
> bi: Blocks sent to a block device (blocks/s).
> bo: Blocks received from a block device (blocks/s).
You might want to have a word with your OS vendor. My vmstat
man page says
IO
bi: Blocks received from a block device (blocks/s).
bo: Blocks sent to a block device (blocks/s).
and certainly anyone who's been around a computer more than a week or
two knows which direction "in" and "out" are customarily seen from.
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, curtisz@norchemlab.com, adave@vantage.com, matt@ymogen.net, pg@rbt.ca
Subject: Re: can't handle large number of INSERT/UPDATEs
In-Reply-To: <15812.1098847291@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