Improving isolationtester's data output
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-hackers@lists.postgresql.org
Date: 2021-06-15T23:03:41Z
Lists: pgsql-hackers
Attachments
- better-isolationtest-output-1.patch (text/x-diff) patch
I've been spending a lot of time looking at isolationtester results over the past couple of days, and gotten really annoyed at how poorly it formats query results. In particular, any column heading or value that is 15 characters or longer is not separated from the next column, rendering the output quite confusing. Attached is a little hack that tries to improve that case while making minimal changes to the output files otherwise. There's still a good deal to be desired here: notably, the code still does nothing to ensure vertical alignment of successive lines when there are wide headings or values. But doing anything about that would involve much-more-invasive changes of the output files. If we wanted to buy into that, I'd think about discarding this ad-hoc code altogether in favor of using one of libpq's fe-print.c routines. But I'm not really sure that the small legibility gains that would result are worth massive changes in the output files. Thoughts? regards, tom lane
Commits
-
Improve display of query results in isolation tests.
- 4a054069a360 14.0 landed
- e535a8899397 9.6.23 landed
- d7da3ef08989 12.8 landed
- b961bdfe1664 13.4 landed
- b1aa0f228465 11.13 landed
- 0a8929ca0b9e 10.18 landed
-
Detect unused steps in isolation specs and do some cleanup
- 484c81bf7765 9.6.23 landed
- feac82fa8550 10.18 landed
- 8f32299424d9 11.13 landed
- 96f3661e4540 12.8 landed
- 989d23b04bea 13.0 cited
-
Remove dry-run mode from isolationtester
- b7cd5c5b02fa 9.6.23 landed
- 0ed218048932 10.18 landed
- 834cb7269166 11.13 landed
- a8f687927eea 12.8 landed
- 9903338b5ea5 13.0 cited