| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Remove dry-run mode from isolationtester |
| Date: | 2019-08-24 02:36:15 |
| Message-ID: | E1i1LuZ-0005SA-CB@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Remove dry-run mode from isolationtester
The original purpose of the dry-run mode is to be able to print all the
possible permutations from a spec file, but it has become less useful
since isolation tests has improved regarding deadlock detection as one
step not wanted by the author could block indefinitely now (originally
the step blocked would have been detected rather quickly). Per
discussion, let's remove it.
Author: Michael Paquier
Reviewed-by: Asim Praveen, Melanie Plageman
Discussion: https://postgr.es/m/20190819080820.GG18166@paquier.xyz
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/9903338b5ea59093d77cfe50ec0b1c22d4a7d843
Modified Files
--------------
src/test/isolation/isolationtester.c | 31 +------------------------------
1 file changed, 1 insertion(+), 30 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-08-24 02:52:51 | pgsql: Detect unused steps in isolation specs and do some cleanup |
| Previous Message | Michael Paquier | 2019-08-23 11:43:39 | pgsql: Improve documentation of pageinspect |