Re: Fix for Extra Parenthesis in pgbench progress message
Tatsuo Ishii <ishii@postgresql.org>
From: Tatsuo Ishii <ishii@postgresql.org>
To: tgl@sss.pgh.pa.us
Cc: nathandbossart@gmail.com, andres@anarazel.de,
masao.fujii@oss.nttdata.com, ishii@postgresql.org,
pgsql-release@lists.postgresql.org, pgsql-hackers@postgresql.org
Date: 2025-02-07T23:26:44Z
Lists: pgsql-hackers
> Nathan Bossart <nathandbossart@gmail.com> writes: >> On Fri, Feb 07, 2025 at 01:10:04PM -0500, Tom Lane wrote: >>> My thought was that duplicating the logic isn't so bad, as attached. > >> WFM! > > It does fix the problem here, so I'll make it so. Sorry for the problem and thank you for the fix! -- Tatsuo Ishii SRA OSS K.K. English: http://www.sraoss.co.jp/index_en/ Japanese:http://www.sraoss.co.jp
Commits
-
Fix pgbench performance issue induced by commit af35fe501.
- b6decfc1d22b 13.19 landed
- 5addea71c7c7 14.16 landed
- 499d1cf55d3d 15.11 landed
- fb056564ec5b 18.0 landed
- e35d396ec354 17.3 landed
- 21b815f92e82 16.7 landed
-
pgbench: Ensure previous progress message is fully cleared when updating.
- f1cb5e51f329 13.19 landed
- 0f13e1a78b14 14.16 landed
- 1e46f7351abc 15.11 landed
- 1cf646957135 16.7 landed
- adb103fcacdd 17.3 landed
- af35fe501af5 18.0 landed