Re: pgbench logging broken by time logic changes

Fabien COELHO <coelho@cri.ensmp.fr>

From: Fabien COELHO <coelho@cri.ensmp.fr>

To: Andrew Dunstan <andrew@dunslane.net>

Cc: Thomas Munro <thomas.munro@gmail.com>, Gregory Smith <gregsmithpgsql@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>, david.christensen@crunchydata.com

Date: 2021-06-17T15:46:47Z

Lists: pgsql-hackers

> Is there an identified issue beyond the concrete example Greg gave of
> the timestamps?

AFAICS, there is a patch which fixes all known issues linked to pgbench 
logging. Whether there exists other issues is possible, but the "broken"
area was quite specific. There are also some TAP tests on pgbench which do 
catch issues.

-- 
Fabien.

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