Re: BUG #17942: vacuumdb doesn't populate extended statistics on partitioned tables

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: henri(dot)chapelle(at)dbandmore(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17942: vacuumdb doesn't populate extended statistics on partitioned tables
Date: 2023-05-29 05:23:05
Message-ID: ZHQ2uUIkRmuY6Glt@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, May 26, 2023 at 06:02:07PM +0900, Kyotaro Horiguchi wrote:
> For 12 or later, pg_partition_ancestors() is available. Thus something
> like the following query would work.

Yes, we will need to be a bit more imaginative for older servers :(

Any pre-11 logic added had better mention the compatibility tweak it
required, and that pg_partition_ancestors() could be used to simplify
the filtering a lot for the analyze case. It would be good to add
some test cases to check all the patterns we would need to look after,
for both the VACUUM and ANALYZE cases. Perhaps with vacuumdb
--verbose and a pattern match check of the logs produced, with at
least 2 level of partitioning to check after the case of ANALYZE run
across a rather complex partitioning tree?
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message José Lorenzo Urdaneta Rodriguez 2023-05-29 13:22:44 Re: Server crash with parallel workers with Postgres 14.7
Previous Message jian he 2023-05-29 00:00:00 Re: Comparing date strings with jsonpath expression