Horton

Re: document the need to analyze partitioned tables

Daniel Gustafsson <daniel@yesql.se>

View thread View on postgr.es
From: Daniel Gustafsson <daniel@yesql.se>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: David Rowley <dgrowleyml@gmail.com>, Bruce Momjian <bruce@momjian.us>, Justin Pryzby <pryzby@telsasoft.com>, Nathan Bossart <nathandbossart@gmail.com>, Tomas Vondra <tomas.vondra@enterprisedb.com>, Robert Haas <robertmhaas@gmail.com>, Álvaro Herrera <alvherre@alvh.no-ip.org>, yuzuko <yuzukohosoya@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2023-08-01T20:24:54Z
Lists: pgsql-hackers 
> On 13 Jul 2023, at 00:21, David Rowley <dgrowleyml@gmail.com> wrote:
> 
> On Wed, 25 Jan 2023 at 21:43, David Rowley <dgrowleyml@gmail.com> wrote:
>> While I agree that the majority of partitions are likely to be
>> relkind='r', which you might ordinarily consider a "normal table", you
>> just might change your mind when you try to INSERT or UPDATE records
>> that would violate the partition constraint. Some partitions might
>> also be themselves partitioned tables and others might be foreign
>> tables. That does not really matter much when it comes to what
>> autovacuum does or does not do, but I'm not really keen to imply in
>> our documents that partitions are "normal tables".
> 
> Based on the above, I'm setting this to waiting on author.

Based on the above, and that the thread has been stalled for months, I'm
marking this returned with feedback.  Please feel free to resubmit a new
version of the patch to a future CF.

--
Daniel Gustafsson

Commits

  1. doc: Fix typo in ANALYZE documentation

  2. Document autoanalyze limitations for partitioned tables

  3. Revert analyze support for partitioned tables

  4. Describe (auto-)analyze behavior for partitioned tables