mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-08-31 21:37:25 +02:00
Stabilize results of insert-conflict-toast.spec.
This back-branch test script was later absorbed into insert-conflict-specconflict.spec, which required some stabilization in commit741d7f104
, so perhaps it's not surprising that it needs a bit of love too. It's odd though that we hadn't seen it fail before now, because I thought that741d7f104
did not change isolationtester's timing behavior for scripts without any annotation markers. In any case, this script is racy on its face, so add an annotation to force stable reporting order. Report: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=piculet&dt=2021-06-24%2009%3A54%3A56 Report: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=petalura&dt=2021-06-24%2010%3A10%3A00
This commit is contained in:
parent
e95f617acc
commit
c6cb62f613
@ -48,4 +48,8 @@ step s3insert {
|
|||||||
INSERT INTO ctoast (key, val) VALUES (1, ctoast_large_val()) ON CONFLICT DO NOTHING;
|
INSERT INTO ctoast (key, val) VALUES (1, ctoast_large_val()) ON CONFLICT DO NOTHING;
|
||||||
}
|
}
|
||||||
|
|
||||||
permutation s2insert s3insert s1commit
|
# s1's commit will release s2 and s3 at the same time, so there's a
|
||||||
|
# race condition as to which finishes first. Annotate the permutation
|
||||||
|
# to always report s2 first.
|
||||||
|
|
||||||
|
permutation s2insert s3insert(s2insert) s1commit
|
||||||
|
Loading…
Reference in New Issue
Block a user