Re: doc: Clarify ANALYZE VERBOSE output
Shinya Kato <shinya11.kato@gmail.com>
From: Shinya Kato <shinya11.kato@gmail.com>
To: maciek@sakrejda.org
Cc: surya poondla <suryapoondla4@gmail.com>, pgsql-docs@lists.postgresql.org
Date: 2026-05-14T12:14:27Z
Lists: pgsql-docs
Attachments
- v2-0001-doc-Clarify-VERBOSE-output-for-ANALYZE-and-VACUUM.patch (application/octet-stream) patch v2-0001
On Tue, May 12, 2026 at 5:15 AM Maciek Sakrejda <m.sakrejda@gmail.com> wrote:
>
> On Tue, May 5, 2026 at 4:26 PM surya poondla <suryapoondla4@gmail.com> wrote:
> > On the wording debate: I think David and Maciek are both pointing at
> > the same real issue, the description should convey (a) "what kind of
> > information" users will see, and (b) "when" they'll see it.
> >
> > Given that, I'd suggest leaning toward something like:
> > "Sends a detailed INFO message to the client for each table as it is processed."
> >
> > I feel with the above message we balance, the server's perspective ("sends" rather than "prints"), and conveys timing ("after each table is processed").
>
> I agree with the analysis, and I think the proposed wording works well.
>
> > This same phrasing could work for both VACUUM and ANALYZE VERBOSE, keeping them consistent.
>
> +1 for consistency.
Sorry for the delayed response, and thank you for the feedback. I
agree with the points raised, so I have updated the patch accordingly.
--
Best regards,
Shinya Kato
NTT OSS Center