From: Tom Lane <tgl@sss.pgh.pa.us>
To: Steve Peterson <stevep-hv@zpfe.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: UPDATE becomes mired / win32
Date: Wed, 04 Oct 2006 16:28:43 -0400
Message-ID: <21179.1159993723@sss.pgh.pa.us> (raw)
In-Reply-To: <6.2.3.4.0.20061004094635.03c114a8@localhost>
References: <6.2.3.4.0.20061004094635.03c114a8@localhost>
Steve Peterson <stevep-hv@zpfe.com> writes:
> If I run the statement:
> (1): UPDATE voter SET gender = 'U';
> on the table in this condition, the query effectively never ends --
> I've allowed it to run for 12-14 hours before giving up.
> ...
> When (1) is running, the machine is very nearly idle, with no
> postmaster taking more than 1 or 2 % of the CPU.
Is the disk busy? If neither CPU nor I/O are saturated, then it's a
good bet that the UPDATE isn't actually running at all, but is waiting
for a lock somewhere. Have you looked into pg_locks to check for a
conflicting lock?
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, stevep-hv@zpfe.com
Subject: Re: UPDATE becomes mired / win32
In-Reply-To: <21179.1159993723@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