Date: Sun, 20 Jun 2021 11:02:14 +0200 (CEST)
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Thomas Munro <thomas.munro@gmail.com>
cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
    Michael Paquier <michael@paquier.xyz>,
    Gregory Smith <gregsmithpgsql@gmail.com>,
    PostgreSQL-development <pgsql-hackers@postgresql.org>,
    david.christensen@crunchydata.com
Subject: Re: pgbench logging broken by time logic changes
In-Reply-To: 
 <CA+hUKGKoUy_DDAR1EWQ8DqqfFY5ApbTTyy7nUJOL2wuNbe2pXQ@mail.gmail.com>
Message-ID: <alpine.DEB.2.22.394.2106201058130.3211875@pseudo>
References: 
 <CA+hUKGKYNgwN=f=WDQ2vGtT_De5oNZ-OfQvtXqe2hBUXKnWFvg@mail.gmail.com>
 <202106200318.gxnon4vrc7t6@alvherre.pgsql>
 <CA+hUKGKXDfQ+ukYAmsnrzNa2dGsEG+BMhMrBXGZ1fyPjP4vZUA@mail.gmail.com>
 <CA+hUKGKoUy_DDAR1EWQ8DqqfFY5ApbTTyy7nUJOL2wuNbe2pXQ@mail.gmail.com>
User-Agent: Alpine 2.22 (DEB 394 2020-01-19)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: 
 <https://www.postgresql.org/message-id/alpine.DEB.2.22.394.2106201058130.3211875%40pseudo>
Precedence: bulk


> Upon reflection, that amounts to the same thing really, so yeah,
> scratch that plan.  I'll defer until after that (and then I'll be
> leaning more towards the revert option).

Sigh. I do not understand anything about the decision processus.

If you do revert, please consider NOT reverting the tps computation 
changes intermixed in the patch.

-- 
Fabien.