diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2010-02-03 03:21:25 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2010-02-03 03:21:25 +0000 |
| commit | 98e314550c3264de02daf3686585683a80dc63c6 (patch) | |
| tree | abdea5135e456f84d1a67e1e9728464f1dbaa711 /src | |
| parent | 70a2b05a59c02464e36d8c9bf23d2eef8502eccd (diff) | |
| download | postgresql-98e314550c3264de02daf3686585683a80dc63c6.tar.gz postgresql-98e314550c3264de02daf3686585683a80dc63c6.zip | |
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.
Diffstat (limited to 'src')
| -rw-r--r-- | src/test/regress/expected/cluster.out | 1 | ||||
| -rw-r--r-- | src/test/regress/sql/cluster.sql | 1 |
2 files changed, 2 insertions, 0 deletions
diff --git a/src/test/regress/expected/cluster.out b/src/test/regress/expected/cluster.out index 23d0a3cd509..96bd8164fa4 100644 --- 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 f3f7a248100..3dea2e4b293 100644 --- 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 - |