Re: doc: Clarify ANALYZE VERBOSE output

From: surya poondla <suryapoondla4(at)gmail(dot)com>
To: Shinya Kato <shinya11(dot)kato(at)gmail(dot)com>
Cc: pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: doc: Clarify ANALYZE VERBOSE output
Date: 2026-05-05 23:26:32
Message-ID: CAOVWO5ov8_JR5Tj2J6cXPZF9cPM3P4w3yhVM9=NeiDMqY3t_PA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Hi All,

Thanks everyone this is a very interesting discussion.

I agree with Shinya that keeping this patch focused is the right call,
documenting every verbose output field is a separate project.

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").

This same phrasing could work for both VACUUM and ANALYZE VERBOSE, keeping
them consistent.

Regards,
Surya Poondla

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message David G. Johnston 2026-05-05 23:27:42 Re: Suspected documentation error
Previous Message PG Doc comments form 2026-05-05 20:35:35 Suspected documentation error