From: Tom Lane <tgl@sss.pgh.pa.us>
To: josh@agliodbs.com
Cc: pgsql-performance@postgresql.org, Abu Mushayeed <abumushayeed@yahoo.com>
Subject: Re: Performance Query
Date: Fri, 02 Mar 2007 21:12:03 -0500
Message-ID: <23598.1172887923@sss.pgh.pa.us> (raw)
In-Reply-To: <200703021652.22785.josh@agliodbs.com>
References: <906038.13110.qm@web57107.mail.re3.yahoo.com>
<200703021652.22785.josh@agliodbs.com>
Josh Berkus <josh@agliodbs.com> writes:
>> Please help in understanding how I can find out what the system is
>> waiting for or why is it taking the query so long.
> First guess would be I/O bound. The planner, at least, thinks you're
> inserting 2 million records. What kind of disk support do you have?
I don't see any need to guess. iostat or vmstat or local equivalent
will show you quick enough if you are maxing out the disk or the CPU.
It seems at least somewhat possible that the thing is blocked on a lock,
in which case the pg_locks view would tell you about it.
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, josh@agliodbs.com, abumushayeed@yahoo.com
Subject: Re: Performance Query
In-Reply-To: <23598.1172887923@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