Re: Improving the isolationtester: fewer failures, less delay
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2021-06-16T01:22:51Z
Lists: pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> Only halfway related: I wonder if we should remove the automatic
> permutation stuff - it's practically never useful. Probably not worth
> changing...
Where it is useful, it saves a lot of error-prone typing ...
> Minor suggestion: I think the folliwing would be a bit easier to read if
> there first were a list of markers, and then separately the longer
> descriptions. Right now it's a bit hard to see which paragraph
> introduces a new type of marker, and which just adds further commentary.
OK, will do. Will act on your other cosmetic points too, tomorrow or so.
>> + if (step_has_blocker(pstep))
>> + {
>> + if (!(flags & STEP_RETRY))
>> + printf("step %s: %s <waiting ...>\n",
>> + step->name, step->sql);
>> + return true;
>> + }
> Might be a bug in my mental state machine: Will this work correctly for
> PSB_ONCE, where we'll already returned before?
This bit ignores PSB_ONCE. Once we've dropped out of try_complete_step
the first time, PSB_ONCE is done affecting things. (I'm not in love
with that symbol name, if you have a better idea.)
regards, tom lane
Commits
-
Use annotations to reduce instability of isolation-test results.
- f228c401b86b 12.8 landed
- e2cde85ef2c3 13.4 landed
- a1417e4378b9 11.13 landed
- 741d7f1047fe 14.0 landed
- 1f32b789de94 10.18 landed
- 13f3fd9e436d 9.6.23 landed