Re: ERROR: corrupt MVNDistinct entry

From: Andrei Lepikhov <lepihov(at)gmail(dot)com>
To: Richard Guo <guofenglinux(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ERROR: corrupt MVNDistinct entry
Date: 2024-12-25 02:33:57
Message-ID: f92106a0-beda-4d97-91c2-3acdafbf0478@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/24/24 15:00, Richard Guo wrote:
> Any thoughts?
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?
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?

--
regards, Andrei Lepikhov

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zhijie Hou (Fujitsu) 2024-12-25 02:43:02 RE: Conflict detection for update_deleted in logical replication
Previous Message Michael Paquier 2024-12-25 01:10:44 Autovacuum giving up on tables after crash because of lack of stats