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 1fd81ddc7710a154834030133c6fea41e55c8efb.camel@cybertec.at
Whole thread Raw
In response to Re: document the need to analyze partitioned tables  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
Responses Re: document the need to analyze partitioned tables
Re: document the need to analyze partitioned tables
List pgsql-hackers
On Mon, 2022-03-28 at 15:05 +0200, Tomas Vondra wrote:
> I've pushed the last version, and backpatched it to 10 (not sure I'd
> call it a bugfix, but I certainly agree with Justin it's worth
> mentioning in the docs, even on older branches).

I'd like to suggest an improvement to this.  The current wording could
be read to mean that dead tuples won't get cleaned up in partitioned tables.


By the way, where are the statistics of a partitioned tables used?  The actual
tables scanned are always the partitions, and in the execution plans that
I have seen, the optimizer always used the statistics of the partitions.

Yours,
Laurenz Albe

Attachment

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Add meson.build to version_stamp.pl
Next
From: Alvaro Herrera
Date:
Subject: Re: [Commitfest 2022-09] Date is Over.