From: Tom Lane <tgl@sss.pgh.pa.us>
To: Justin Pryzby <pryzby@telsasoft.com>
cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Release notes for February minor releases
In-reply-to: <20220204210214.GR23027@telsasoft.com>
References: <425850.1644004739@sss.pgh.pa.us> <20220204210214.GR23027@telsasoft.com>
Comments: In-reply-to Justin Pryzby <pryzby@telsasoft.com>
	message dated "Fri, 04 Feb 2022 15:02:14 -0600"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <433897.1644010159.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 04 Feb 2022 16:29:19 -0500
Message-ID: <433898.1644010159@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/433898.1644010159%40sss.pgh.pa.us>
Precedence: bulk

Justin Pryzby <pryzby@telsasoft.com> writes:
> On Fri, Feb 04, 2022 at 02:58:59PM -0500, Tom Lane wrote:
>> Please send comments/corrections by Sunday.

[ assorted comments ]

Thanks for the corrections.

> +      A previous bug fix disabled building of extended statistics for
> +      old-style inheritance trees, but any existing statistics data was
> +      not removed, and that data would become more and more out-of-date
> +      over time.  Adjust the planner to ignore such data.  Extended
> +      statistics for the individual child tables are still built and us=
ed,
> +      however.

> The issue here isn't that old stats were never updated.  For inheritance=
, they
> *were* updated with non-inherited stats (for SELECT FROM ONLY).  But the=
n
> "SELECT FROM tbl*" used the stats anyway...

I'm confused about this bit.  Are we still building bogus stats for
inheritance parents, or has that stopped?

			regards, tom lane