Re: Doc: clarify the log message level of the VERBOSE option
Masahiro Ikeda <ikedamsh@oss.nttdata.com>
From: Masahiro Ikeda <ikedamsh@oss.nttdata.com>
To: Yugo Nagata <nagata@sraoss.co.jp>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2024-12-05T01:39:22Z
Lists: pgsql-hackers
Attachments
- v2-0001-Doc-clarify-the-log-message-level-of-the-VERBOSE-.patch (text/x-diff) patch v2-0001
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
Commits
-
doc: Clarify log level for VERBOSE messages in maintenance commands.
- 632384d0eb14 18.0 landed