Julio Leyva wrote [09/29/2006 03:11 PM]:
Actually these are the messages when we ran the test with 2 backends
(postgresql 8.14)
...
So The messages in the previous e-mail is when we ran the test just
with one backend
The test still run, but is extremly slow with sequoia, I believe because
of the deadlock, however when we run the aplication without sequoia
there is no deadlock reported by postgresql.
The traces you get with your 2 backends/raidb1 config are "normal":
sequoia detects a deadlock condition in your application, chooses a
victim, and notifies with ERROR and WARN messages.
Sequoia enforces a slightly stronger locking that postgresql in order to
guarantee consitency on backends. This extra consitency constraint can
cause 'artificial' deadlock conditions which would not happen when
running directly against the db.
2006-09-28 14:25:00,805 WARN backend.DatabaseBackend.testdb1 No
transaction medatada found for transaction 13952628 releasing locks
manually
2006-09-28 14:25:00,807 WARN backend.DatabaseBackend.testdb2 No
transaction medatada found for transaction 13952628 releasing
These two look strange however... but I have no clue as to why it is
related to your problem.
A+O.
_______________________________________________
Sequoia mailing list
[EMAIL PROTECTED]
https://forge.continuent.org/mailman/listinfo/sequoia
