This reverts commit
2268e6afd596. It turned out that inconsistency in
the report is still possible, so go back to the simpler formulation of
the test and instead add an alternate expected output.
Discussion: https://postgr.es/m/
20180103193728.ysqpcp2xjnqpiep7@alvherre.pgsql
-Parsed test spec with 3 sessions
+Parsed test spec with 2 sessions
-starting permutation: s2l s1i s2i s3u
-pg_advisory_lock
-
-
+starting permutation: s2l s1i s2i
step s2l: SELECT pg_advisory_lock(281457);
pg_advisory_lock
<waiting ...>
step s2i:
CREATE INDEX CONCURRENTLY mcic_two_pkey ON mcic_two (id)
- WHERE unlck() AND lck_shr(572814);
- <waiting ...>
-step s3u: SELECT unlck();
+ WHERE unlck();
+
+step s1i: <... completed>
unlck
t
-step s1i: <... completed>
-step s2i: <... completed>
--- /dev/null
+Parsed test spec with 2 sessions
+
+starting permutation: s2l s1i s2i
+step s2l: SELECT pg_advisory_lock(281457);
+pg_advisory_lock
+
+
+step s1i:
+ CREATE INDEX CONCURRENTLY mcic_one_pkey ON mcic_one (id)
+ WHERE lck_shr(281457);
+ <waiting ...>
+step s2i:
+ CREATE INDEX CONCURRENTLY mcic_two_pkey ON mcic_two (id)
+ WHERE unlck();
+ <waiting ...>
+step s1i: <... completed>
+step s2i: <... completed>
+unlck
+
+t
step "s1i" {
CREATE INDEX CONCURRENTLY mcic_one_pkey ON mcic_one (id)
WHERE lck_shr(281457);
-}
-step "s1u" { SELECT unlck(); }
+ }
+teardown { SELECT unlck(); }
session "s2"
step "s2l" { SELECT pg_advisory_lock(281457); }
step "s2i" {
CREATE INDEX CONCURRENTLY mcic_two_pkey ON mcic_two (id)
- WHERE unlck() AND lck_shr(572814);
+ WHERE unlck();
}
-session "s3"
-setup { SELECT pg_advisory_lock(572814); }
-step "s3u" { SELECT unlck(); }
-
-permutation "s2l" "s1i" "s2i" "s3u"
+permutation "s2l" "s1i" "s2i"