Re: pgbench logging broken by time logic changes

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, 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-17 11:49:47
Message-ID: alpine.DEB.2.22.394.2106171157370.2693553@pseudo
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> I found you forgot to fix printProgressReport().

Indeed.

> Also, according to the document, interval_start in Aggregated Logging
> seems to be printed in seconds instead of ms.

Indeed. I'm unsure about what we should really want there, but for a beta
bug fix I agree that it must simply comply to the old documented behavior.

> The attached patch includes these fixes.

Thanks. Works for me.

--
Fabien.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2021-06-17 11:57:08 Re: locking [user] catalog tables vs 2pc vs logical rep
Previous Message Amit Kapila 2021-06-17 11:37:01 Re: Unresolved repliaction hang and stop problem.