mirror of
https://github.com/postgres/postgres.git
synced 2025-07-28 23:42:10 +03:00
Detect unused steps in isolation specs and do some cleanup
This is useful for developers to find out if an isolation spec is over-engineered or if it needs more work by warning at the end of a test run if a step is not used, generating a failure with extra diffs. While on it, clean up all the specs which include steps not used in any permutations to simplify them. This is a backpatch of989d23b
and06fdc4e
, as it is becoming useful to make all the branches consistent for an upcoming patch that will improve the output generated by isolationtester. Author: Michael Paquier Reviewed-by: Asim Praveen, Melanie Plageman Discussion: https://postgr.es/m/20190819080820.GG18166@paquier.xyz Discussion: https://postgr.es/m/794820.1623872009@sss.pgh.pa.us Backpatch-through: 9.6
This commit is contained in:
@ -26,7 +26,6 @@ step "s0_sub_get_base_snap" { INSERT INTO dummy VALUES (0); }
|
||||
step "s0_insert" { INSERT INTO harvest VALUES (1, 2, 3); }
|
||||
step "s0_end_sub0" { RELEASE SAVEPOINT s0; }
|
||||
step "s0_end_sub1" { RELEASE SAVEPOINT s1; }
|
||||
step "s0_insert2" { INSERT INTO harvest VALUES (1, 2, 3, 4); }
|
||||
step "s0_commit" { COMMIT; }
|
||||
step "s0_get_changes" { SELECT data FROM pg_logical_slot_get_changes('isolation_slot', NULL, NULL, 'include-xids', '0', 'skip-empty-xacts', '1'); }
|
||||
|
||||
|
Reference in New Issue
Block a user