Hello,
step lsto: SET lock_timeout = 5000; SET statement_timeout = 6000;
step update: DELETE FROM accounts WHERE accountid = 'checking'; <waiting ...>
step update: <... completed>
-ERROR: canceling statement due to lock timeout
+ERROR: canceling statement due to statement timeout
No matter how slow the machine is, how can you manage to get statement
timeout to fire first? Given the coding that prefers lock timeouts if
there is a tie (unlikely), but otherwise processes them in registered
time order (assuming the clock only travels forward), well, I must be
missing something...
--
Thomas Munro
http://www.enterprisedb.com