Re: Doc: clarify the log message level of the VERBOSE option

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: Masahiro Ikeda <ikedamsh(at)oss(dot)nttdata(dot)com>, Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Doc: clarify the log message level of the VERBOSE option
Date: 2024-12-19 17:57:02
Message-ID: 398f4380-b7c7-4dbb-ac40-db2766476fbe@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2024/12/05 16:48, Masahiro Ikeda wrote:
> On 2024-12-05 16:23, Yugo NAGATA wrote:
>>
>> -      Prints a progress report as each table is clustered.
>> +      Prints a progress report as each table is clustered,
>> +      at <literal>INFO</literal> level.
>>
>>
>> I feel like the comma could not be necessary here like the fix for
>> the ANALYZE document, but it might be better to wait for a review
>> from a native English speaker.
>
> Thanks. OK, I'll wait.

I'm not a native English speaker, but barring any objection,
I'd like to commit the attached patch. In this patch,
I've just removed a comma and updated the commit log message.

Regards,

--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

Attachment Content-Type Size
v3-0001-doc-Clarify-log-level-for-VERBOSE-messages-in-mai.patch text/plain 3.0 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Yugo Nagata 2024-12-19 18:22:26 Allow ILIKE forward matching to use btree index
Previous Message Jeff Davis 2024-12-19 17:51:32 Re: Add CASEFOLD() function.