Re: document the need to analyze partitioned tables
От | Bruce Momjian |
---|---|
Тема | Re: document the need to analyze partitioned tables |
Дата | |
Msg-id | Y8q5Jf8D9SXs/uvr@momjian.us обсуждение исходный текст |
Ответ на | Re: document the need to analyze partitioned tables (Laurenz Albe <laurenz.albe@cybertec.at>) |
Список | pgsql-hackers |
On Fri, Jan 20, 2023 at 10:33:57AM +0100, Laurenz Albe wrote: > 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". We have it already: Have autoanalyze of parent tables occur when child tables are modified > 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? Yes. -- Bruce Momjian <bruce@momjian.us> https://momjian.us EDB https://enterprisedb.com Embrace your flaws. They make you human, rather than perfect, which you will never be.
В списке pgsql-hackers по дате отправления: