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
Date: Fri, 23 Sep 2005 07:30:22 -0600
Message-ID: <20050923133021.GA72851@winnie.fuhr.org> (raw)
In-Reply-To: <ED153B99D71F5B4ABE318CF841A5C3E60206139C@RPIDALEXC004.corp.realpage.com>
References: <ED153B99D71F5B4ABE318CF841A5C3E60206139C@RPIDALEXC004.corp.realpage.com>
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
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-sql@postgresql.org
Cc: mike@fuhr.org, kenneth.hutchinson@mpfyieldstar.com
Subject: Re: Issue with UPDATE statement on v8
In-Reply-To: <20050923133021.GA72851@winnie.fuhr.org>
* 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