BUG #5107: Lock never released - Mailing list pgsql-bugs

From Christian DUPONT
Subject BUG #5107: Lock never released
Date
Msg-id 200910090839.n998dubk016726@wwwmaster.postgresql.org
Whole thread Raw
Responses Re: BUG #5107: Lock never released
List pgsql-bugs
The following bug has been logged online:

Bug reference:      5107
Logged by:          Christian DUPONT
Email address:      christian.dupont@cegelec.com
PostgreSQL version: 8.3
Operating system:   RHEL 5
Description:        Lock never released
Details:

Hi,

I use slony 1 v 1.2.14.

After an unexpected stop, several tables remained locked :

sl_log_1 -> RowExclusiveLock,
sl_log_status -> AccessShareLock,
sl_action_seq -> AccessShareLock,
h_jou_pmvdata -> RowExclusiveLock (data table).

This has happened a couple of times, even though I don't have a way to
reproduce it. A database restart does not help. Because of these locks, I
can't get rid (truncate / delete) of the tables nor even dump the db.

Only solution : destroy and rebuild from the master database (it is
replicated after all).

I would be glad to send any information needed to investigate.

pgsql-bugs by date:

Previous
From: "Mohamed Altamimi"
Date:
Subject: BUG #5106: Relationship between two tables
Next
From: Tom Lane
Date:
Subject: Re: BUG #5107: Lock never released