From: Jim C. Nasby <decibel@decibel.org>
To: Greg Stark <gsstark@mit.edu>
Cc: pgsql-performance@postgresql.org
Subject: Re: Slow copy with little CPU/disk usage
Date: Wed, 20 Apr 2005 17:23:02 -0500
Message-ID: <20050420222302.GX58835@decibel.org> (raw)
In-Reply-To: <87d5sqdq24.fsf@stark.xeocode.com>
References: <20050420020033.GZ58835@decibel.org>
<87d5sqdq24.fsf@stark.xeocode.com>
No, he's using either COPY or \COPY.
On Wed, Apr 20, 2005 at 12:34:27AM -0400, Greg Stark wrote:
> "Jim C. Nasby" <decibel@decibel.org> writes:
>
> > What's really odd is that neither the CPU or the disk are being
> > hammered. The box appears to be pretty idle; the postgresql proces is
> > using 4-5% CPU.
>
> Is he committing every row? In that case you would see fairly low i/o
> bandwidth usage because most of the time is being spent seeking and waiting
> for rotational latency.
>
> --
> greg
>
--
Jim C. Nasby, Database Consultant decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
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: decibel@decibel.org, gsstark@mit.edu
Subject: Re: Slow copy with little CPU/disk usage
In-Reply-To: <20050420222302.GX58835@decibel.org>
* 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