Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: row-level deadlock problem
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
- Cc: Kamil Kaczkowski <kamil(at)kamil(dot)eisp(dot)pl>, pgsql-general(at)postgresql(dot)org
- Subject: Re: row-level deadlock problem
- Date: Sat, 27 Nov 2004 12:58:36 -0500
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes: > Well, there has to be something, since an UPDATE in Read Committed mode > simply doesn't have any locks that can deadlock. You're mistaken; it takes a row lock on each row it updates. I'm not sure why the two UPDATEs are visiting the same rows in different orders, but if they do the failure is certainly possible. regards, tom lane
- Follow-Ups:
- Re: row-level deadlock problem
- From: Alvaro Herrera
- Re: row-level deadlock problem
- References:
- row-level deadlock problem
- From: Kamil Kaczkowski
- Re: row-level deadlock problem
- From: Tom Lane
- Re: row-level deadlock problem
- From: Kamil Kaczkowski
- Re: row-level deadlock problem
- From: Tom Lane
- Re: row-level deadlock problem
- From: Kamil Kaczkowski
- Re: row-level deadlock problem
- From: Martijn van Oosterhout
- Re: row-level deadlock problem
- From: Kamil Kaczkowski
- Re: row-level deadlock problem
- From: Martijn van Oosterhout
- row-level deadlock problem
- Prev by Date: Re: Can one alter the format of a numeric column?
- Next by Date: Re: how many JOINs?
- Previous by thread: Re: row-level deadlock problem
- Next by thread: Re: row-level deadlock problem
- Indexes: