Re: [GENERAL] share lock error

2006-10-05 Thread Tom Lane
Terry Fielder <[EMAIL PROTECTED]> writes: > 7.4.3 Yoi. You need to think about an update. > And the records are gone from pg_locks, how much time after the deadlock > do I have before they are purged? Approximately none --- pg_locks is a live view. regards, tom lane -

Re: [GENERAL] share lock error

2006-10-05 Thread Terry Fielder
7.4.3 And the records are gone from pg_locks, how much time after the deadlock do I have before they are purged? Terry Fielder [EMAIL PROTECTED] Associate Director Software Development and Deployment Great Gulf Homes / Ashton Woods Homes Fax: (416) 441-9085 Tom Lane wrote: Terry Fielde

Re: [GENERAL] share lock error

2006-10-05 Thread Tom Lane
Terry Fielder <[EMAIL PROTECTED]> writes: > I am getting this in my log file: > 2006-10-05 16:06:23 [6469] ERROR: deadlock detected > DETAIL: Process 6469 waits for ShareLock on transaction 668582701; > blocked by process 28763. > Process 28763 waits for ShareLock on transaction 66858632

Re: [GENERAL] share lock error

2006-10-05 Thread Erik Jones
In the pg_locks system view there are 'pid', and 'relation' columns (there's also a 'transaction' column but the pid will work just fine). Do a look up on that table using the pids from the error messages. The values for relation can be used to look up the table in pg_class. Something like t

[GENERAL] share lock error

2006-10-05 Thread Terry Fielder
I am getting this in my log file: 2006-10-05 16:06:23 [6469] ERROR: deadlock detected DETAIL: Process 6469 waits for ShareLock on transaction 668582701; blocked by process 28763. Process 28763 waits for ShareLock on transaction 668586325; blocked by process 6469. I believe the scenari