| From: | Shinya Kato <shinya11(dot)kato(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, maciek(at)sakrejda(dot)org, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: doc: Clarify ANALYZE VERBOSE output |
| Date: | 2026-04-08 01:49:24 |
| Message-ID: | CAOzEurS7aNO=TnZztwnxJdLgmNnmotwcocxVR2s4qLrZ66ZkxQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Mon, Apr 6, 2026, 14:17 David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
>
> How about something like:
> “Enables sending an INFO message to the client (and server log) as each
> table is processed. This message contains: etc…”
>
> And then let’s tell the user what info they are getting and what it means
> (where necessary).
>
> I concur being specific about when these messages arrive, and IMO where,
> should be specified. But losing the detail of “report” is not good; but
> not sure why we are being vague so suggest we just go all-in on specificity.
>
Thank you for the suggestion. I'd prefer to keep this patch focused; since
the verbose output of both commands is subject to change, listing every
individual field in the documentation would require frequent updates.
I believe the current "Outputs" section is intentionally kept simple to
minimize maintenance overhead. While expanding it might be a worthwhile
follow-up, it probably deserves its own dedicated discussion.
--
Shinya Kato
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2026-04-10 03:00:38 | Clarify log_parameter_max_length docs regarding log_min_duration_statement vs log_duration |
| Previous Message | Dapeng Wang | 2026-04-07 05:31:40 | doc: add examples section to earthdistance documentation |