| From: | Mark van Leeuwen <markvl(at)internode(dot)on(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Exclusive row locks not release |
| Date: | 2012-01-20 07:18:04 |
| Message-ID: | 4F19152C.1000705@internode.on.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 20/01/2012 4:40 PM, Tom Lane wrote:
> Mark van Leeuwen<markvl(at)internode(dot)on(dot)net> writes:
>> I have a case where exclusive row locks have been placed on a table and
>> I don't what process has the locks or how they might be released.
>> The locks are still there even after I have restarted the database.
> Uncommitted prepared transaction, perhaps? Look into pg_prepared_xacts.
>
> regards, tom lane
>
Yes, that was it. Don't have much experience with Postgresql - had
expected all locks would have been released by stopping the database.
I used ROLLBACK PREPARED transaction_id to remove the locks.
Thanks for your help,
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | P. Broennimann | 2012-01-20 08:20:51 | dblink (INSERT ..... RETURNING) |
| Previous Message | Tom Lane | 2012-01-20 05:40:39 | Re: Exclusive row locks not release |