Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 98e3145

Browse files
committed
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.
1 parent 70a2b05 commit 98e3145

File tree

2 files changed

+2
-0
lines changed

2 files changed

+2
-0
lines changed

src/test/regress/expected/cluster.out

+1
Original file line numberDiff line numberDiff line change
@@ -446,6 +446,7 @@ select * from clstr_temp;
446446
2 | two
447447
(2 rows)
448448

449+
drop table clstr_temp;
449450
-- clean up
450451
\c -
451452
DROP TABLE clustertest;

src/test/regress/sql/cluster.sql

+1
Original file line numberDiff line numberDiff line change
@@ -192,6 +192,7 @@ create temp table clstr_temp (col1 int primary key, col2 text);
192192
insert into clstr_temp values (2, 'two'), (1, 'one');
193193
cluster clstr_temp using clstr_temp_pkey;
194194
select * from clstr_temp;
195+
drop table clstr_temp;
195196

196197
-- clean up
197198
\c -

0 commit comments

Comments
 (0)