Commitc6cb62f

committed

Stabilize results of insert-conflict-toast.spec.

This back-branch test script was later absorbed intoinsert-conflict-specconflict.spec, which required some stabilizationin commit741d7f1, so perhaps it's not surprising that it needs abit of love too.It's odd though that we hadn't seen it fail before now, becauseI thought that741d7f1 did not change isolationtester's timingbehavior for scripts without any annotation markers. In any case,this script is racy on its face, so add an annotation to force stablereporting order.Report:https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=piculet&dt=2021-06-24%2009%3A54%3A56Report:https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=petalura&dt=2021-06-24%2010%3A10%3A00

1 parente95f617 commitc6cb62fCopy full SHA for c6cb62f

File tree

-1

lines changed

-1

lines changed

Lines changed: 5 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -48,4 +48,8 @@ step s3insert {`
`48`	`48`	`INSERTINTOctoast (key,val)VALUES (1,ctoast_large_val())ONCONFLICTDONOTHING;`
`49`	`49`	`}`
`50`	`50`
`51`		`-permutations2inserts3inserts1commit`
	`51`	`+# s1's commit will release s2 and s3 at the same time, so there's a`
	`52`	`+# race condition as to which finishes first. Annotate the permutation`
	`53`	`+# to always report s2 first.`
	`54`	`+`
	`55`	`+permutations2inserts3insert(s2insert)s1commit`

Comments

(0)