Re: document the need to analyze partitioned tables - Mailing list pgsql-hackers

From Laurenz Albe
Subject Re: document the need to analyze partitioned tables
Date
Msg-id 80e6fed85b4d0ad278c3dd8dc6eb2e0837a57fc3.camel@cybertec.at
Whole thread Raw
In response to Re: document the need to analyze partitioned tables  (Bruce Momjian <bruce@momjian.us>)
Responses Re: document the need to analyze partitioned tables
List pgsql-hackers
On Thu, 2023-01-19 at 15:56 -0500, Bruce Momjian wrote:
> On Thu, Jan 19, 2023 at 01:50:05PM +0100, Laurenz Albe wrote:
> > On Wed, 2023-01-18 at 16:23 -0500, Bruce Momjian wrote:
> > > Is it possible to document when partition table statistics helps?
> >
> > I think it would be difficult to come up with an exhaustive list.
>
> I was afraid of that.  I asked only because most people assume
> autovacuum handles _all_ statistics needs, but this case is not handled.
> Do people even have any statistics maintenance process anymore, and if
> not, how would they know they need to run a manual ANALYZE?

Probably not.  I think this would warrant an entry in the TODO list:
"make autovacuum collect startistics for partitioned tables".

Even if we cannot give better advice than "run ALANYZE manually if
the execution plan looks fishy", the patch is still an improvement,
isn't it?

I have already seen several questions by people who read the current
documentation and were worried that autovacuum wouldn't clean up their
partitioned tables.

Yours,
Laurenz Albe



pgsql-hackers by date:

Previous
From: Maxim Orlov
Date:
Subject: Re: Add SHELL_EXIT_CODE to psql
Next
From: Jelte Fennema
Date:
Subject: Re: run pgindent on a regular basis / scripted manner