Increase timeout in statement_timeout test from 1 second to 2 seconds.

We have once or twice seen failures suggesting that control didn't get
to the exception block before the timeout elapsed, which is unlikely
but not impossible in a parallel regression test (with a dozen other
backends competing for cycles).  This change doesn't completely prevent
the problem of course, but it should reduce the probability enough that
we don't see it anymore.  Per buildfarm results.

diff --git a/src/test/regress/expected/plpgsql.out b/src/test/regress/expected/plpgsql.out
index 6e6597dadb2f452a7880e74c9295101efb570810..e776c8f33cdc8166990641657303f304b63f2fcc 100644 (file)
--- a/src/test/regress/expected/plpgsql.out
+++ b/src/test/regress/expected/plpgsql.out
@@ -2019,7 +2019,7 @@ begin
   begin
     x := x + 1;
     insert into foo values(x);
-    -- we assume this will take longer than 1 second:
+    -- we assume this will take longer than 2 seconds:
     select count(*) into x from tenk1 a, tenk1 b, tenk1 c;
   exception
     when others then
@@ -2032,7 +2032,7 @@ begin
   insert into foo values(x);
   return x;
 end$$ language plpgsql;
-set statement_timeout to 1000;
+set statement_timeout to 2000;
 select blockme();
 NOTICE:  nyeah nyeah, can't stop me
  blockme 

diff --git a/src/test/regress/sql/plpgsql.sql b/src/test/regress/sql/plpgsql.sql
index 19e145be65f359bc3c3d22318cab92656e31c0f0..86aa2ec05740eb278f4ee7a2db4c7251d7f3d221 100644 (file)
--- a/src/test/regress/sql/plpgsql.sql
+++ b/src/test/regress/sql/plpgsql.sql
@@ -1755,7 +1755,7 @@ begin
   begin
     x := x + 1;
     insert into foo values(x);
-    -- we assume this will take longer than 1 second:
+    -- we assume this will take longer than 2 seconds:
     select count(*) into x from tenk1 a, tenk1 b, tenk1 c;
   exception
     when others then
@@ -1769,7 +1769,7 @@ begin
   return x;
 end$$ language plpgsql;
 
-set statement_timeout to 1000;
+set statement_timeout to 2000;
 
 select blockme();