Re: Fix for Extra Parenthesis in pgbench progress message
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Tatsuo Ishii <ishii@postgresql.org>
Cc: masao.fujii@oss.nttdata.com, pgsql-hackers@postgresql.org
Date: 2024-11-28T00:10:57Z
Lists: pgsql-hackers
On Thu, Nov 28, 2024 at 07:45:09AM +0900, Tatsuo Ishii wrote: > Yeah, maybe git apply is not smart enough. `git apply` is more picky than a simple `patch -p1` as it checks more context around the patch and is more likely to reject some input. When the former does not work correctly, I personally just use the latter, dealing with file additions and removals manually. -- Michael
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