Re: ERROR: corrupt MVNDistinct entry

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Andrei Lepikhov <lepihov(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ERROR: corrupt MVNDistinct entry
Date: 2024-12-25 08:14:53
Message-ID: CAMbWs4_wMCPZqRyTyTYc4R+2JMW6ozL-mnRwTMkVmee0jQPL3Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Dec 25, 2024 at 11:34 AM Andrei Lepikhov <lepihov(at)gmail(dot)com> 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hayato Kuroda (Fujitsu) 2024-12-25 08:25:20 RE: Logical replication timeout
Previous Message Richard Guo 2024-12-25 07:49:30 Re: ERROR: corrupt MVNDistinct entry