RE: analyze-in-stages post upgrade questions - Mailing list pgsql-general

From Zechman, Derek S
Subject RE: analyze-in-stages post upgrade questions
Date
Msg-id PH0PR04MB8294E796D6297D4E3BE4EFB6C049A@PH0PR04MB8294.namprd04.prod.outlook.com
Whole thread Raw
In response to Re: analyze-in-stages post upgrade questions  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: analyze-in-stages post upgrade questions
List pgsql-general
> > Well, that wouldn't explain why it doesn't work on partitioned tables.
> > I am under the impression that it should.
> >
> > Derek, can cou share the pg_stats entries for the partitioned table?
> 
> There are no entries in pg_stats for the parent table until after I manually run an analyze on it – Example below
 
You are right.  I looked at the code, and "vacuumdb" does not process
partitiond tables, even if --analyze-only is specified.  I find that
surprising, aince the SQL command ANALYZE (without a table name) will
also collect statistics for partitioned tables.
 
I think that it would be a good idea to change that behavior.
In particular, it makes a lot of sense to collect statistics for
partitioned tables after a "pg_upgrade".
 
Attached is a patch to make "vacuumdb --analyze-only" consider
partitioned tables as well.
 
Yours,
Laurenz Albe
 
Is there a plan to include this patch in future releases/patches of postgres? 
 
Thanks,
(Derek) Sean

pgsql-general by date:

Previous
From: Shlok Kyal
Date:
Subject: Re: error “server process was terminated by signal 11: Segmentation fault” running pg_create_logical_replication_slot using pgoutput plugin
Next
From: Alpaslan AKDAĞ
Date:
Subject: Password Encryption and Connection Issues