MIME-Version: 1.0
References: 
 <CAOzEurTpMTUEW8kHu-zKB0EBtuPfpvyoJ--8pxKe87p24BGrpg@mail.gmail.com>
In-Reply-To: 
 <CAOzEurTpMTUEW8kHu-zKB0EBtuPfpvyoJ--8pxKe87p24BGrpg@mail.gmail.com>
From: surya poondla <suryapoondla4@gmail.com>
Date: Tue, 5 May 2026 16:26:32 -0700
Message-ID: 
 <CAOVWO5ov8_JR5Tj2J6cXPZF9cPM3P4w3yhVM9=NeiDMqY3t_PA@mail.gmail.com>
Subject: Re: doc: Clarify ANALYZE VERBOSE output
To: Shinya Kato <shinya11.kato@gmail.com>
Cc: pgsql-docs@lists.postgresql.org
Content-Type: multipart/alternative; boundary="00000000000049fcd306511a6186"
Archived-At: 
 <https://www.postgresql.org/message-id/CAOVWO5ov8_JR5Tj2J6cXPZF9cPM3P4w3yhVM9%3DNeiDMqY3t_PA%40mail.gmail.com>
Precedence: bulk

--00000000000049fcd306511a6186
Content-Type: text/plain; charset="UTF-8"

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

--00000000000049fcd306511a6186
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hi All,<br><br>Thanks everyone this is a =
very interesting discussion.<br><br>I agree with Shinya that keeping this p=
atch focused is the right call,<br>documenting every verbose output field i=
s a separate project.<br><br>On the wording debate: I think David and Macie=
k are both pointing at<br>the same real issue, the description should conve=
y (a) &quot;what kind of<br>information&quot; users will see, and (b) &quot=
;when&quot; they&#39;ll see it.<br><br>Given that, I&#39;d suggest leaning =
toward something like:<br>&quot;Sends a detailed INFO message to the client=
 for each table as it=C2=A0is processed.&quot;<br><br>I feel with=C2=A0the =
above message we balance, the server&#39;s perspective (&quot;sends&quot; r=
ather than &quot;prints&quot;), and conveys timing (&quot;after each table =
is processed&quot;).=C2=A0<br><br>This same phrasing could work for both VA=
CUUM and ANALYZE VERBOSE, keeping them consistent.<br></div><div dir=3D"ltr=
"><br></div><div>Regards,=C2=A0<br>Surya Poondla</div></div>

--00000000000049fcd306511a6186--