| From: | Sami Imseih <samimseih(at)gmail(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | 河田達也 <kawatatatsuya0913(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCH] Add sampling statistics to autoanalyze log output |
| Date: | 2026-01-07 22:22:02 |
| Message-ID: | CAA5RZ0tHUrAtD2uMwZeOdQota3ASpVOD20bXETC4cKej2n3xTQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Thanks for the work on this, and I agree that the logging between a manual
ANALYZE and autoanalyze should be unified. +1
I have a few comments:
1/ Wouldn’t it be better to combine the new sampling output fields into a
single struct? This is more idiomatic, similar to BufferUsage or WalUsage,
and it would also make the API easier to extend in the future. Right now,
changing the function signature breaks the AcquireSampleRowsFunc ABI,
which is acceptable for a major release, but using a struct would help
avoid future breaks if we ever add more sampling data in later releases.
```
@@ -535,11 +546,15 @@ do_analyze_rel(Relation onerel, const VacuumParams params,
if (inh)
numrows = acquire_inherited_sample_rows(onerel, elevel,
rows, targrows,
-
&totalrows, &totaldeadrows);
+
&totalrows, &totaldeadrows,
+
&totalpages, &scannedpages,
+
&sampleliverows, &sampledeadrows);
else
numrows = (*acquirefunc) (onerel, elevel,
rows, targrows,
-
&totalrows, &totaldeadrows);
+
&totalrows, &totaldeadrows,
+
&totalpages, &scannedpages,
+
&sampleliverows, &sampledeadrows);
```
2/ I think this patch should just focus on unifying the existing logging only.
The " estimated total rows" for a foreign table should be a separate
thread/patch, IMO.
3/ You should also run pgindent.
Regards,
--
Sami Imseih
Amazon Web Services (AWS)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chao Li | 2026-01-07 22:45:01 | Re: Remove deprecated role membership options from psql help for CREATE USER/GROUP |
| Previous Message | David G. Johnston | 2026-01-07 22:17:39 | Re: docs: clarify ALTER TABLE behavior on partitioned tables |