From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] How to get info about deadlocks? |
Date: | 1999-11-29 06:04:41 |
Message-ID: | 199911290604.BAA07345@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> I've been experimenting with concurrent VACUUMs and getting occasional
> instances of
>
> NOTICE: Deadlock detected -- See the lock(l) manual page for a possible cause.
> ERROR: WaitOnLock: error on wakeup - Aborting this transaction
>
> It would be really nice if I could find out the particular locks that
> are causing this conflict --- but the code that emits these messages
> isn't very transparent :-(. Can anyone explain how to determine just
> what the deadlock is?
>
Massimo has some. See the top of lock.c for pg_options flags to dump
out locks.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1999-11-29 06:09:41 | Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions |
Previous Message | Vadim Mikheev | 1999-11-29 05:59:22 | Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions |