Horton

Re: pgbench logging broken by time logic changes

Fabien COELHO <coelho@cri.ensmp.fr>

View thread View on postgr.es
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Michael Paquier <michael@paquier.xyz>
Cc: Andrew Dunstan <andrew@dunslane.net>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Thomas Munro <thomas.munro@gmail.com>, Gregory Smith <gregsmithpgsql@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>, david.christensen@crunchydata.com
Date: 2021-06-30T07:45:47Z
Lists: pgsql-hackers

Attachments

Bonjour Michaël,

> Okay, I have extracted this part from your patch, and back-patched
> this fix down to 11.  The comments were a good addition, so I have
> kept them.  I have also made the second regex of check_pgbench_logs()
> pickier with the client ID value expected, as it can only be 0.

Attached the remaining part of the patch to fix known issues on pgbench 
logging.

I've added an entry on the open item on the wiki. I'm unsure about who the 
owner should be.

-- 
Fabien.

Commits

  1. Fix pgbench timestamp bugs.

  2. Fix pattern matching logic for logs in TAP tests of pgbench

  3. pgbench: Improve time logic.

  4. pgbench: Synchronize client threads.

  5. pgbench: refactor handling of stats tracking