Re: Effective deadlock handling

From: Daniel Morgan <damorgan_at_x.washington.edu>
Date: Mon, 05 Jan 2004 16:55:24 -0800
Message-ID: <1073350438.164855@yasure>

Galen Boyer wrote:

> On Mon, 05 Jan 2004, damorgan_at_x.washington.edu wrote:
>
>

>>The records stay in the "deadlocked" state until the
>>transaction is completed by either a commit or rollback. So the
>>problem is also mostly solvable by performing incremental
>>commits.

>
>
> A single transaction involving multiple SQL statements should be
> broken up and commits should be issued throughout? Are you going
> to have a clean-up process for this as well?

I'm going to continue to write SELECT FOR UPDATE SKIP LOCKED. I was merely pointing out to the OP that more frequent commits is one technique for minimizing deadlocks. It comes with its own price in performance and ORA-01555s but it something that should be on the table and considered.

-- 
Daniel Morgan
http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp
http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp
damorgan_at_x.washington.edu
(replace 'x' with a 'u' to reply)

Received on Mon Jan 05 2004 - 18:55:24 CST