Increase deadlock_timeout to 100ms in FK isolation tests

The previous value of 20ms is dangerously close to the time actually
spent just waiting for the deadlock to happen, so on occasion it causes
the test to fail simply because the other session didn't get to run
early enough, not managing to cause the deadlock that needs to be
detected.  With this new value, it's expected that most machines on
normal load will be able to pass the test.

Author: Noah Misch
pull/1/head
Alvaro Herrera 14 years ago
parent a0eae1a2ee
commit d6db0e4e0e
  1. 2
      src/test/isolation/specs/fk-deadlock.spec
  2. 2
      src/test/isolation/specs/fk-deadlock2.spec

@ -19,7 +19,7 @@ teardown
}
session "s1"
setup { BEGIN; SET deadlock_timeout = '20ms'; }
setup { BEGIN; SET deadlock_timeout = '100ms'; }
step "s1i" { INSERT INTO child VALUES (1, 1); }
step "s1u" { UPDATE parent SET aux = 'bar'; }
step "s1c" { COMMIT; }

@ -24,7 +24,7 @@ teardown
}
session "s1"
setup { BEGIN; SET deadlock_timeout = '20ms'; }
setup { BEGIN; SET deadlock_timeout = '100ms'; }
step "s1u1" { UPDATE A SET Col1 = 1 WHERE AID = 1; }
step "s1u2" { UPDATE B SET Col2 = 1 WHERE BID = 2; }
step "s1c" { COMMIT; }

Loading…
Cancel
Save