Re: Avoid stuck of pbgench due to skipped transactions

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
Cc: Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Avoid stuck of pbgench due to skipped transactions
Date: 2021-09-07 09:24:39
Message-ID: alpine.DEB.2.22.394.2109071121360.56739@pseudo
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Hello Fujii-san,

> Stop counting skipped transactions under -T as soon as the timer is
> exceeded. Because otherwise it can take a very long time to count all of
> them especially when quite a lot of them happen with unrealistically
> high rate setting in -R, which would prevent pgbench from ending
> immediately. Because of this behavior, note that there is no guarantee
> that all skipped transactions are counted under -T though there is under
> -t. This is OK in practice because it's very unlikely to happen with
> realistic setting.

Ok, I find this text quite clear.

> One question is; which version do we want to back-patch to?

If we consider it a "very minor bug fix" which is triggered by somehow
unrealistic options, so I'd say 14 & dev, or possibly only dev.

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nitin Jadhav 2021-09-07 09:37:15 Re: when the startup process doesn't (logging startup delays)
Previous Message Peter Eisentraut 2021-09-07 09:22:24 Re: Remove Value node struct