Re: Fix for Extra Parenthesis in pgbench progress message
Fujii Masao <masao.fujii@oss.nttdata.com>
From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: Tatsuo Ishii <ishii@postgresql.org>
Cc: pgsql-hackers@postgresql.org
Date: 2024-11-25T16:32:10Z
Lists: pgsql-hackers
Attachments
- v5-0001-pgbench-Ensure-previous-progress-message-is-fully-pg13-14.patch (text/plain) patch v5-0001
- v5-0001-pgbench-Ensure-previous-progress-message-is-fully-pg15-16.patch (text/plain) patch v5-0001
- v5-0001-pgbench-Ensure-previous-progress-message-is-fully-pg17-master.patch (text/plain) patch v5-0001
On 2024/11/25 8:31, Tatsuo Ishii wrote: > Now that two minor releases are out, are you going to commit and > back-patch this? Yes, I will. But, the patch didn't apply cleanly to some back branches, so I've created and attached updated patches for them. Could you review these? If they look good, I'll proceed with pushing them. Regards, -- Fujii Masao Advanced Computing Technology Center Research and Development Headquarters NTT DATA CORPORATION
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