Re: Defects with invalid stats data for expressions in extended stats
Corey Huinker <corey.huinker@gmail.com>
From: Corey Huinker <corey.huinker@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>,
Tomas Vondra <tomas@vondra.me>
Date: 2026-02-27T04:50:19Z
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.
Commits
-
test_custom_types: Test module with fancy custom data types
- 858c83b3e666 14.23 landed
- 8eedbc2cc4b3 15.18 landed
- c0676c8294f7 16.14 landed
- d4f33d026a6b 17.10 landed
- 017e4e395d0d 18.4 landed
- 2176520089e8 19 (unreleased) landed
-
Fix set of issues with extended statistics on expressions
- 038c7d4a3b24 14.23 landed
- f033abc6c4f2 15.18 landed
- 04745ba9c72e 16.14 landed
- 530b6b02f891 17.10 landed
- 83671c0da049 18.4 landed
- 3b7a6fa15720 19 (unreleased) landed