From: Michael Fuhr <mike@fuhr.org>
To: Dan Harris <fbsd@drivefaster.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Table locking problems?
Date: Tue, 9 Aug 2005 12:52:01 -0600
Message-ID: <20050809185201.GA25325@winnie.fuhr.org> (raw)
In-Reply-To: <52CFA236-FC43-4018-B399-1854240110FF@drivefaster.net>
References: <52CFA236-FC43-4018-B399-1854240110FF@drivefaster.net>
On Tue, Aug 09, 2005 at 12:04:11PM -0600, Dan Harris wrote:
> These changes have definitely improved performance, but I am now
> finding some trouble with UPDATE or DELETE queries "hanging" and
> never releasing their locks. As this happens, other statements queue
> up behind it.
Have you examined pg_locks to see if the UPDATE or DELETE is blocked
because of a lock another session holds?
Are you using foreign keys? When updating referencing rows, released
versions of PostgreSQL acquire a lock on the referenced row that can
hurt concurrency or cause deadlock (this will be improved in 8.1).
--
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-performance@postgresql.org
Cc: mike@fuhr.org, fbsd@drivefaster.net
Subject: Re: Table locking problems?
In-Reply-To: <20050809185201.GA25325@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