X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id A9D5FD9117
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Fri, 23 Sep 2005 10:30:33 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 64763-08
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Fri, 23 Sep 2005 13:30:29 +0000 (GMT)
Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158])
	by svr1.postgresql.org (Postfix) with ESMTP id 7A121D908E
	for <pgsql-sql@postgresql.org>; Fri, 23 Sep 2005 10:30:28 -0300 (ADT)
Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1])
	by tigger.fuhr.org (8.13.3/8.13.3) with ESMTP id j8NDUMlF058381
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Fri, 23 Sep 2005 07:30:25 -0600 (MDT)
	(envelope-from mfuhr@winnie.fuhr.org)
Received: from winnie.fuhr.org (localhost [127.0.0.1])
	by winnie.fuhr.org (8.13.3/8.13.3) with ESMTP id j8NDUM2e072944;
	Fri, 23 Sep 2005 07:30:22 -0600 (MDT)
	(envelope-from mfuhr@winnie.fuhr.org)
Received: (from mfuhr@localhost)
	by winnie.fuhr.org (8.13.3/8.13.3/Submit) id j8NDUMEE072943;
	Fri, 23 Sep 2005 07:30:22 -0600 (MDT) (envelope-from mfuhr)
Date: Fri, 23 Sep 2005 07:30:22 -0600
From: Michael Fuhr <mike@fuhr.org>
To: Kenneth Hutchinson <kenneth.hutchinson@mpfyieldstar.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Issue with UPDATE statement on v8
Message-ID: <20050923133021.GA72851@winnie.fuhr.org>
References: 
 <ED153B99D71F5B4ABE318CF841A5C3E60206139C@RPIDALEXC004.corp.realpage.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <ED153B99D71F5B4ABE318CF841A5C3E60206139C@RPIDALEXC004.corp.realpage.com>
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.005 required=5 tests=[AWL=0.005]
X-Spam-Level: 
X-Archive-Number: 200509/225
X-Sequence-Number: 22772

On Thu, Sep 22, 2005 at 11:22:22AM -0500, Kenneth Hutchinson wrote:
> UPDATE t_summary
> SET        availability = 7
> WHERE  oid = 28245084
> 
> When this query is executed (within a function or without) the database
> will simply hang.  If the UPDATE is turned into a SELECT, the query
> works just fine.

One possibility is that another transaction has updated this row
or done a SELECT FOR UPDATE and hasn't committed yet.  Does just
this one record cause the update to hang or do all updates to the
table hang?  Have you queried pg_locks in another session while the
update is hung?

-- 
Michael Fuhr