public inbox for [email protected]
help / color / mirror / Atom feedFrom: Richard Guo <[email protected]>
To: Andrei Lepikhov <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: ERROR: corrupt MVNDistinct entry
Date: Wed, 25 Dec 2024 17:14:53 +0900
Message-ID: <CAMbWs4_wMCPZqRyTyTYc4R+2JMW6ozL-mnRwTMkVmee0jQPL3Q@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAMbWs4-2Z4k+nFTiZe0Qbu5n8juUWenDAtMzi98bAZQtwHx0-w@mail.gmail.com>
<[email protected]>
On Wed, Dec 25, 2024 at 11:34 AM Andrei Lepikhov <[email protected]> wrote:
> I have a couple of notes.
> 1. The nulling_relids provides us sensible information about possible
> nulls inside the input. We are not using it to estimate the number of
> such nulls for now. Does Your idea consist of obtaining 'clear'
> statistics and reusing nulling_relids knowledge somewhere later?
Are you referring to the nullfrac estimates? A RelOptInfo's
nulling_relids records all above outer joins that can null this rel.
However, I cannot see how it helps with nullfrac.
> 2. It is ok for Vars. But what about expressions? We use equal() in
> distinct, MCV and dependencies modules. Do we need to remove nulls
> before using extended statistics as a general rule?
AFAIU, the expressions in extended statistics are not decorated with
any nullingrels bits, are they?
Thanks
Richard
view thread (6+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: ERROR: corrupt MVNDistinct entry
In-Reply-To: <CAMbWs4_wMCPZqRyTyTYc4R+2JMW6ozL-mnRwTMkVmee0jQPL3Q@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox