Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit98e3145

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 temptable created in the previous session hadn't finished getting dropped.Unluckily, I didn't see this in several repetitions of the parallelregression tests, but it's popping up on quite a few buildfarm machines.
1 parent70a2b05 commit98e3145

File tree

2 files changed

+2
-0
lines changed

2 files changed

+2
-0
lines changed

‎src/test/regress/expected/cluster.out

Lines changed: 1 addition & 0 deletions
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

Lines changed: 1 addition & 0 deletions
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_tempvalues (2,'two'), (1,'one');
193193
cluster clstr_temp using clstr_temp_pkey;
194194
select*from clstr_temp;
195+
droptable clstr_temp;
195196

196197
-- clean up
197198
\c-

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp