Re: pgbench logging broken by time logic changes

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, Gregory Smith <gregsmithpgsql(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, david(dot)christensen(at)crunchydata(dot)com
Subject: Re: pgbench logging broken by time logic changes
Date: 2021-06-20 14:15:55
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 6/20/21 5:02 AM, Fabien COELHO wrote:
>> 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.

Yes, sometimes it passeth all understanding.

There will certainly be a BETA3, and in every recent year except last
year there has been a BETA4.

If this were core server code threatening data integrity I would be
inclined to be more strict, but after all pg_bench is a utility program,
and I think we can allow a little more latitude.



Andrew Dunstan

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-06-20 14:45:21 Re: PXGS vs TAP tests
Previous Message Nikolay Shaplov 2021-06-20 14:03:15 Re: [PATCH] Finally split StdRdOptions into HeapOptions and ToastOptions