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

From: Masahiro Ikeda <ikedamsh(at)oss(dot)nttdata(dot)com>
To: 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-05 01:39:22
Message-ID: 800450ba7e24dc6998a191e97c75d0b8@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2024-12-04 21:08, Yugo Nagata wrote:
> This would prevent other users from make a misunderstanding as you did.
>
> I found the description on amvalidate also explains a message is
> output at INFO level.
> ( https://www.postgresql.org/docs/devel/index-functions.html )
>
> Problems should be reported with ereport messages, typically at INFO
> level.
>
> I don't know the actual intention to mention the message level here,
> but
> this might have the same purpose of you.

Thanks for your response!

> Should we add the description for CLUSTER command, since
> it also has the VERBOSE options?

Yes, you're right. I missed it.

> - Enables display of progress messages.
> + Prints a detailed analyze activity report for each table as
> + <literal>INFO</literal> messages.
>
> Do we need rewrite the description in addition to mentioning the
> message level?

Since the messages for the VERBOSE options look similar, I unified the
descriptions
for VACUUM, ANALYZE, and REINDEX. However, I don’t have a strong opinion
on this.
I’ve fixed it in the v2 patch.

Regards,
--
Masahiro Ikeda
NTT DATA CORPORATION

Attachment Content-Type Size
v2-0001-Doc-clarify-the-log-message-level-of-the-VERBOSE-.patch text/x-diff 2.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2024-12-05 01:46:33 Re: [Bug] Heap Use After Free in parallel_vacuum_reset_dead_items Function
Previous Message Tom Lane 2024-12-05 01:25:14 Re: Cannot find a working 64-bit integer type on Illumos