mirror of
https://github.com/postgres/postgres.git
synced 2025-07-23 03:21:12 +03:00
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.
This commit is contained in:
@ -446,6 +446,7 @@ select * from clstr_temp;
|
|||||||
2 | two
|
2 | two
|
||||||
(2 rows)
|
(2 rows)
|
||||||
|
|
||||||
|
drop table clstr_temp;
|
||||||
-- clean up
|
-- clean up
|
||||||
\c -
|
\c -
|
||||||
DROP TABLE clustertest;
|
DROP TABLE clustertest;
|
||||||
|
@ -192,6 +192,7 @@ create temp table clstr_temp (col1 int primary key, col2 text);
|
|||||||
insert into clstr_temp values (2, 'two'), (1, 'one');
|
insert into clstr_temp values (2, 'two'), (1, 'one');
|
||||||
cluster clstr_temp using clstr_temp_pkey;
|
cluster clstr_temp using clstr_temp_pkey;
|
||||||
select * from clstr_temp;
|
select * from clstr_temp;
|
||||||
|
drop table clstr_temp;
|
||||||
|
|
||||||
-- clean up
|
-- clean up
|
||||||
\c -
|
\c -
|
||||||
|
Reference in New Issue
Block a user