Steve Peterson <[EMAIL PROTECTED]> 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

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Reply via email to