Re: pgbench logging broken by time logic changes

Andrew Dunstan <andrew@dunslane.net>

From: Andrew Dunstan <andrew@dunslane.net>

To: Fabien COELHO <coelho@cri.ensmp.fr>, 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

Date: 2021-06-20T14:15:55Z

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.

cheers

andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

Commits

Fix pgbench timestamp bugs.
- 5614a0f78eaa 14.0 landed
- 0e39a608ed55 15.0 landed
Fix pattern matching logic for logs in TAP tests of pgbench
- 0efd2a1a66dd 11.13 landed
- 79ff96aa9d9a 12.8 landed
- 7a9eaf111ac0 13.4 landed
- c13585fe9e55 14.0 landed
pgbench: Improve time logic.
- 547f04e7348b 14.0 cited
pgbench: Synchronize client threads.
- aeb57af8e640 14.0 cited
pgbench: refactor handling of stats tracking
- b60376649600 9.6.0 cited