Horton

Re: Improving isolationtester's data output

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
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-17T03:01:31Z
Lists: pgsql-hackers 
On Wed, Jun 16, 2021 at 09:10:25PM -0400, Tom Lane wrote:
> Yeah, it only results in a message in the output file anyway.

That itself would blow up the buildfarm, as 06fdc4e has proved.

> Yes please.

Nobody has complained about the removal of --dry-run with 13~.  The
second one would cause tests to fail after a minor upgrade for
extensions using isolationtester, but it seems like a good thing to
inform people about anyway.  So, okay, both parts are done.
--
Michael

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