Fix timing-sensitive regression test result I just created :-( --- the

DROP USER at the end of the cluster.sql test could fail, if the temp
table created in the previous session hadn't finished getting dropped.
Unluckily, I didn't see this in several repetitions of the parallel
regression tests, but it's popping up on quite a few buildfarm machines.

diff --git a/src/test/regress/expected/cluster.out b/src/test/regress/expected/cluster.out
index 23d0a3cd509ccc5ba0f54740cdb0732076d13a66..96bd8164fa4d19bf48c20b619213b492446dd976 100644 (file)
--- a/src/test/regress/expected/cluster.out
+++ b/src/test/regress/expected/cluster.out
@@ -446,6 +446,7 @@ select * from clstr_temp;
     2 | two
 (2 rows)
 
+drop table clstr_temp;
 -- clean up
 \c -
 DROP TABLE clustertest;

diff --git a/src/test/regress/sql/cluster.sql b/src/test/regress/sql/cluster.sql
index f3f7a248100975bbcc14f91d515e4c3dc89a1810..3dea2e4b2932a20f219f39abb3168bf943f193b2 100644 (file)
--- a/src/test/regress/sql/cluster.sql
+++ b/src/test/regress/sql/cluster.sql
@@ -192,6 +192,7 @@ create temp table clstr_temp (col1 int primary key, col2 text);
 insert into clstr_temp values (2, 'two'), (1, 'one');
 cluster clstr_temp using clstr_temp_pkey;
 select * from clstr_temp;
+drop table clstr_temp;
 
 -- clean up
 \c -