public inbox for pgsql-docs@postgresql.org  

help / color / mirror / Atom feed

From: surya poondla <suryapoondla4@gmail.com>
To: Shinya Kato <shinya11.kato@gmail.com>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: doc: Clarify ANALYZE VERBOSE output
Date: Tue, 5 May 2026 16:26:32 -0700
Message-ID: <CAOVWO5ov8_JR5Tj2J6cXPZF9cPM3P4w3yhVM9=NeiDMqY3t_PA@mail.gmail.com> (raw)
In-Reply-To: <CAOzEurTpMTUEW8kHu-zKB0EBtuPfpvyoJ--8pxKe87p24BGrpg@mail.gmail.com>
References: <CAOzEurTpMTUEW8kHu-zKB0EBtuPfpvyoJ--8pxKe87p24BGrpg@mail.gmail.com>

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

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: suryapoondla4@gmail.com, shinya11.kato@gmail.com, pgsql-docs@lists.postgresql.org
  Subject: Re: doc: Clarify ANALYZE VERBOSE output
  In-Reply-To: <CAOVWO5ov8_JR5Tj2J6cXPZF9cPM3P4w3yhVM9=NeiDMqY3t_PA@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox