From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Release notes for February minor releases |
Date: | 2022-02-04 21:49:28 |
Message-ID: | 435414.1644011368@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Justin Pryzby <pryzby(at)telsasoft(dot)com> writes:
> On Fri, Feb 04, 2022 at 04:29:19PM -0500, Tom Lane wrote:
>> I'm confused about this bit. Are we still building bogus stats for
>> inheritance parents, or has that stopped?
> To make a long story long:
> - before 859b3003de, an ERROR occurred when a stats object was created on an
> inheritance parent.
> - To avoid the error, 859b3003de changed to no longer build "whole tree" stats
> on the table heirarchy. Non-inheried stats were still collected.
> - However, the stats were *also* applied to inherited queries (FROM tbl*).
> 36c4bc6 stops applying stats that shouldn't be applied (and doesn't change
> their collection during ANALYZE).
Got it. So we collected (and still do collect) non-inherited stats
for inheritance parents, but prior to 36c4bc6 those were mistakenly
applied in estimating both inheritance and non-inheritance queries.
Now we only do the latter.
(Since 269b532ae, this is all better in HEAD, but that's not
relevant for the back-branch release notes.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-02-04 22:12:43 | Re: support for CREATE MODULE |
Previous Message | Alvaro Herrera | 2022-02-04 21:48:11 | Re: support for CREATE MODULE |