From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: anole's failed timeouts test |
Date: | 2019-02-11 04:08:13 |
Message-ID: | 11596.1549858093@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> writes:
> 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?
The statement timer starts running first; the lock timer only starts
to run when we begin to wait for a lock. So if the session goes to
sleep for > 1 second in between those events, this is unsurprising.
There are a bunch of tests in timeouts.spec that are unreasonably
slow because the timeouts have been whacked until even very slow/
overloaded machines will pass the tests. Maybe we need to tweak
this one too.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2019-02-11 04:31:54 | Re: Inadequate executor locking of indexes |
Previous Message | Justin Pryzby | 2019-02-11 04:01:32 | Re: pg11.1: dsa_area could not attach to segment |