Horton

Re: Improving isolationtester's data output

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, Noah Misch <noah@leadboat.com>, Andres Freund <andres@anarazel.de>, pgsql-hackers@lists.postgresql.org
Date: 2021-06-17T01:10:25Z
Lists: pgsql-hackers 
Michael Paquier <michael@paquier.xyz> writes:
> On Wed, Jun 16, 2021 at 03:33:29PM -0400, Tom Lane wrote:
>> After checking cross-version diffs to see how painful that is likely
>> to be, I'm inclined to also back-patch Michael's v13 commits
>> 989d23b04beac0c26f44c379b04ac781eaa4265e
>> Detect unused steps in isolation specs and do some cleanup
>> 9903338b5ea59093d77cfe50ec0b1c22d4a7d843
>> Remove dry-run mode from isolationtester

> There may be tests in stable branches that define steps remaining
> unused, but that's a minimal risk.

Yeah, it only results in a message in the output file anyway.

> Down to which version do you need
> these?  All the way down to 9.6?

Yes please.

			regards, tom lane

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