Received: from localhost (pluto.hub.org [200.46.204.4]) by postgresql.org (Postfix) with ESMTP id 38B9C9FA333 for ; Sat, 4 Nov 2006 05:08:55 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.4]) (amavisd-new, port 10024) with ESMTP id 71346-07 for ; Sat, 4 Nov 2006 05:08:50 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.185]) by postgresql.org (Postfix) with ESMTP id 73FE49F93A0 for ; Sat, 4 Nov 2006 05:08:43 -0400 (AST) Received: by nf-out-0910.google.com with SMTP id x37so1863230nfc for ; Sat, 04 Nov 2006 01:08:41 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FmCO9YQw2ZI9kqbQ/S+x1Ay8cM2d9mx68EcAlGnTqbf1Qw3570Cm7lQY7bFC6dn2xHFscy5G3PDMThap2tPdJtlUBvjoMcEoH7hhtepbK50hD9Z1c/JKRILXruQTMdJrYg/t6bobb3wxkCnAOk2B+FV8m/UU4JKtik9pIrk8SM8= Received: by 10.82.111.8 with SMTP id j8mr966157buc.1162631321316; Sat, 04 Nov 2006 01:08:41 -0800 (PST) Received: by 10.82.161.3 with HTTP; Sat, 4 Nov 2006 01:08:40 -0800 (PST) Message-ID: <1f30b80c0611040108n5235c135qe5fff990f1636e76@mail.gmail.com> Date: Sat, 4 Nov 2006 14:08:40 +0500 From: imad To: "Dylan Lorimer" Subject: Re: Long SQL Update Question Cc: pgsql-sql@postgresql.org In-Reply-To: <3ddac38d0611031421s3c3f48ffoeea9a9bd1f86a71c@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3ddac38d0611031421s3c3f48ffoeea9a9bd1f86a71c@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/50 X-Sequence-Number: 26702 You can turn on logging ... but your transaction would be even slower after that. The following links should give you some pointers: http://www.postgresql.org/docs/8.1/static/monitoring-stats.html http://www.postgresql.org/docs/8.1/static/monitoring.html Also try Nagios monitoring plugins for PostgreSQL. Get it from pgFoundry. --Imad www.EnterpriseDB.com On 11/4/06, Dylan Lorimer wrote: > So I kicked off a SQL transaction that has been running for 30+ minutes. Is > there any way to monitor it to know if it has possibly hanged or not? To be > fair, it is an update on 4+ million rows, so I expect it to run for a bit. > But any stats or metrics I can get would be helpful. > Cheers, > dylan >