Horton

Re: Improving isolationtester's data output

Andres Freund <andres@anarazel.de>

View thread View on postgr.es
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, pgsql-hackers@lists.postgresql.org
Date: 2021-06-16T01:31:15Z
Lists: pgsql-hackers 
Hi,

On 2021-06-15 19:26:25 -0400, Tom Lane wrote:
> Going forward it wouldn't be a problem, but back-patching isolation
> test cases might find it annoying.  On the other hand, my nearby
> patch to improve isolation test stability is already going to create
> issues of that sort.  (Unless, dare I say it, we back-patch that.)

It might be worth to back-patch - aren't there some back branch cases of
test instability? And perhaps more importantly, I'm sure we'll encounter
cases of writing new isolation tests in the course of fixing bugs that
we'd want to backpatch that are hard to make reliable without the new
features?

Greetings,

Andres Freund

Commits

  1. Improve display of query results in isolation tests.

  2. Detect unused steps in isolation specs and do some cleanup

  3. Remove dry-run mode from isolationtester