cks
and how to avoid them.
Number of deadlock events during one day is so big that it looks like it
happens everytime two updatestats function are running concurrently.
All sugestions are welcomed, thanks in advance.
--
Kamil Kaczkowski
[EMAIL PROTECTED]
---(end of b
On Fri, 26 Nov 2004, Tom Lane wrote:
> Kamil Kaczkowski <[EMAIL PROTECTED]> writes:
> > I have problems with deadlocks caused by(at least I think so) row-level
> > locks and I can't find the reason.
>
> The failure seems clearly a deadlock on row-level locks. Are
d
... some other activity on table test ...
T2: UPDATE started(with different order then T1's update)
DEADLOCK
If it looks like this, I'm probably lucky it didn't bite me before.
Best regards.
--
Kamil Kaczkowski
[EMAIL PROTECTED]
---(end of broa
On Sat, 27 Nov 2004, Martijn van Oosterhout wrote:
> On Sat, Nov 27, 2004 at 03:20:16AM +0100, Kamil Kaczkowski wrote:
> > > Change things so you don't need to update more than one row per query,
> > > perhaps? The lack of any primary key on that table was already pret
f it, possibility of such event should be very low, but I'm
getting 2000 deadlocks during busy day.
Regards.
--
Kamil Kaczkowski
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 8: explain analyze is your friend
7;d change
anything.
I agree it looks like we're missing something. Any other theories,
suggestions what should I check?
I'll try to isolate problem to test case by writing scripts to simulate actual
load but it'll take same time.
Regards.
--
Kamil Kaczkowski
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 8: explain analyze is your friend
