Re: [GENERAL] insert deadlock

2005-12-06 Thread Greg Stark
Brian Cox <[EMAIL PROTECTED]> writes: > Thread 1 does 1+ inserts into Table A and 1 update of Table B in a single > transaction. > This thread runs on demand. > > Thread 2 does 1+ inserts into Table C in a separate transaction. This thread > runs once an hour. I suspect you'll have to include

Re: [GENERAL] insert deadlock

2005-12-06 Thread Tom Lane
Brian Cox <[EMAIL PROTECTED]> writes: > There are no foreign key constraints from/to A or B to/from C. How sure are you of that? FK conflicts are much the most common reason for unexpected deadlocks in pre-8.1 PG releases. > 2005-12-02 15:04:46,773 [TP-Processor8] INFO > [com.timestock.tess.ser

[GENERAL] insert deadlock

2005-12-06 Thread Brian Cox
Thread 1 does 1+ inserts into Table A and 1 update of Table B in a single transaction. This thread runs on demand. Thread 2 does 1+ inserts into Table C in a separate transaction. This thread runs once an hour. There are no foreign key constraints from/to A or B to/from C. The default isola