Re: Improving isolationtester's data output

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Noah Misch <noah(at)leadboat(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Improving isolationtester's data output
Date: 2021-06-17 00:16:01
Message-ID: YMqUQWSaaFP5UAy6@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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
>
> as those touched some of the same code areas, and it doesn't seem like
> there'd be any harm in making these aspects uniform across all the
> branches. If Michael wants to do that back-patching himself, that's
> fine with me, otherwise I'll do it.

There may be tests in stable branches that define steps remaining
unused, but that's a minimal risk. Down to which version do you need
these? All the way down to 9.6?
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2021-06-17 00:23:17 Re: PoC: Using Count-Min Sketch for join cardinality estimation
Previous Message Tom Lane 2021-06-16 23:40:18 Re: A qsort template