Re: analyze-in-stages post upgrade questions

> On 7 Aug 2026, at 06:30, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:

> Attached is an updated v3 patch. Barring any objections, I'll commit it.

No objection, v3 LGTM.

> While looking at this, I found one related point. This patch only uses
> ANALYZE ONLY for partitioned tables. However, since v18, plain ANALYZE
> on an inheritance parent also recursively analyzes its inheritance
> children. Therefore, when vacuumdb automatically enumerates both an
> inheritance parent and its child tables, the child tables can still be
> analyzed twice: once via the parent and once as separately selected
> targets.
>
> This seems similar to the partitioned-table issue fixed here, but
> it strikes me as an enhancement rather than a stabilization fix for v19.
> If we decide to address it, I think it would be better targeted at v20.
> Does that sound reasonable?

Agreed, this is v20 material. If we want to do anything for 18/19 it would be
to document this, once the suggested patch for v20 is done it might inform us
whether that would be useful or if we should keep it v20 only.

--
Daniel Gustafsson