| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, yuzuko <yuzukohosoya(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: document the need to analyze partitioned tables |
| Date: | 2023-07-12 22:21:34 |
| Message-ID: | CAApHDvqmadnbpKVJHohL+5iM-6egqE4eo34W-B3C4D93WnbhxA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 25 Jan 2023 at 21:43, David Rowley <dgrowleyml(at)gmail(dot)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.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2023-07-12 22:25:54 | Re: 'ERROR: attempted to update invisible tuple' from 'ALTER INDEX ... ATTACH PARTITION' on parent index |
| Previous Message | David G. Johnston | 2023-07-12 22:12:50 | Re: CommandStatus from insert returning when using a portal. |