| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | masao(dot)fujii(at)oss(dot)nttdata(dot)com |
| Cc: | btogiwarayuushi(at)oss(dot)nttdata(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Fix for Extra Parenthesis in pgbench progress message |
| Date: | 2024-11-24 23:31:55 |
| Message-ID: | 20241125.083155.1820744655877715597.ishii@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Fujii-san,
> On 2024/11/08 11:47, Tatsuo Ishii wrote:
>> I think you need to adjust
>> fprintf(stderr, "%*c\r", chars - 1, ' '); /* Clear the current line */
>> to:
>> fprintf(stderr, "%*c\r", chars, ' '); /* Clear the current line */
>> since now chars does not consider the EOL char. By clearing chars - 1,
>> the closing parenthesis will be left on the screen.
>
> You're right! I've updated the patch and attached v4.
>
> About the back-patch: initially, there were concerns it might be too
> invasive,
> as you told upthread. However, after our discussion, I think the
> latest version
> is straightforward enough, and I'm okay with back-patching
> it. Thoughts?
>
> Since the minor release freeze is already in effect, if we commit this
> patch,
> we'll need to wait until the next minor releases are out next week
> before
> the commit and back-patch.
Now that two minor releases are out, are you going to commit and
back-patch this?
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2024-11-25 00:42:49 | Re: On non-Windows, hard depend on uselocale(3) |
| Previous Message | David Rowley | 2024-11-24 21:54:38 | Re: Use or not record count on examples |