mirror of
https://github.com/postgres/postgres.git
synced 2025-07-05 07:21:24 +03:00
Use PG_TEST_TIMEOUT_DEFAULT for pg_regress suite non-elapsing timeouts.
Currently, only contrib/test_decoding has this property. Use \getenv to load the timeout value. Discussion: https://postgr.es/m/20220218052842.GA3627003@rfd.leadboat.com
This commit is contained in:
@ -34,7 +34,10 @@ declare
|
||||
updated3 bool;
|
||||
updated4 bool;
|
||||
begin
|
||||
-- we don't want to wait forever; loop will exit after 30 seconds
|
||||
-- We don't want to wait forever. No timeout suffices if the OS drops our
|
||||
-- stats traffic because an earlier test file left a full UDP buffer.
|
||||
-- Hence, don't use PG_TEST_TIMEOUT_DEFAULT, which may be large for
|
||||
-- can't-happen timeouts. Exit after 30 seconds.
|
||||
for i in 1 .. 300 loop
|
||||
|
||||
-- With parallel query, the seqscan and indexscan on tenk2 might be done
|
||||
|
@ -33,7 +33,10 @@ declare
|
||||
updated3 bool;
|
||||
updated4 bool;
|
||||
begin
|
||||
-- we don't want to wait forever; loop will exit after 30 seconds
|
||||
-- We don't want to wait forever. No timeout suffices if the OS drops our
|
||||
-- stats traffic because an earlier test file left a full UDP buffer.
|
||||
-- Hence, don't use PG_TEST_TIMEOUT_DEFAULT, which may be large for
|
||||
-- can't-happen timeouts. Exit after 30 seconds.
|
||||
for i in 1 .. 300 loop
|
||||
|
||||
-- With parallel query, the seqscan and indexscan on tenk2 might be done
|
||||
|
Reference in New Issue
Block a user