Re: [HACKERS] Foreign key quandries

2003-02-28 Thread Rod Taylor
Gah, hit wrong key combination and the email sent early. Anyway, after that 'sleep' mess at the bottom is: T1 or T2: Sleeping too long -- lets run deadlock detection code T1 or T2: Kill off random participant of deadlock. The other participant is then allowed to continue their work. On Sat, 2003

[HACKERS] Foreign key quandries

2003-02-28 Thread Stephan Szabo
Going through the issues in doing dirty reads in foreign keys I've come up with a few cases that I'm fairly uncertain about how to handle with regards to deadlocks and figured I should ask for advice because I think I'm missing something painfully obvious, but don't get large enough blocks of time