Re: Defects with invalid stats data for expressions in extended stats

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tomas Vondra <tomas(at)vondra(dot)me>
Subject: Re: Defects with invalid stats data for expressions in extended stats
Date: 2026-02-27 04:50:19
Message-ID: CADkLM=dqmnrX+MuS6bAfE3wA9NHte_z=KpcvJLJp0_g0pfMTmA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> No, that's on purpose. Using a SQL function with a body would not
> trigger the problem with the stats loaded at the end of the SQL test
> as we would skip the fatal call of statext_expressions_load(). Based
> on your confusion, I guess that a note to document that is in order,
> at least, so as nobody comes with the idea of changing the definition
> of this function..
>

Thanks for the explanation. Changes look good.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Yura Sokolov 2026-02-27 05:00:28 Re: Fix bug in multixact Oldest*MXactId initialization and access
Previous Message Bertrand Drouvot 2026-02-27 04:46:31 Use pg_icu_unicode_version(void) instead of pg_icu_unicode_version()