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 10df82cfc2463cc7f79fe49e506656e67bc3394e..bc12bb46fcfb926b42f44f3b7cc6ba473d30b1ef 100644 (file)
--- a/src/test/regress/expected/plpgsql.out
+++ b/src/test/regress/expected/plpgsql.out
@@ -1902,7 +1902,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
@@ -1915,7 +1915,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 62aa3543479629302deed5620683af5162ef3923..fbcdcca7679c54a4476eadda91ba90537e92bfd6 100644 (file)
--- a/src/test/regress/sql/plpgsql.sql
+++ b/src/test/regress/sql/plpgsql.sql
@@ -1674,7 +1674,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
@@ -1688,7 +1688,7 @@ begin
   return x;
 end$$ language plpgsql;
 
-set statement_timeout to 1000;
+set statement_timeout to 2000;
 
 select blockme();