Re: Is there value in having optimizer stats for joins/foreignkeys?

Alexandra Wang <alexandra.wang.oss@gmail.com>

From: Alexandra Wang <alexandra.wang.oss@gmail.com>

To: jian he <jian.universality@gmail.com>

Cc: pgsql-hackers@lists.postgresql.org, Tomas Vondra <tomas@vondra.me>, Andrei Lepikhov <lepihov@gmail.com>, Corey Huinker <corey.huinker@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, hs@cybertec.at, Jeff Davis <pgsql@j-davis.com>

Date: 2026-05-14T23:13:26Z

Lists: pgsql-hackers

Attachments

v5-0001-Add-join-MCV-statistics-for-selectivity-estimatio.patch (application/octet-stream) patch v5-0001

Patch needed a rebase, so here's v5.

I've dropped the changes to catversion.h so hopefully I won't need to
rebase too often. Sorry about the noise!

While I was at it, I also addressed the issues Jian mentioned -- all
minor fixes in parse_utilcmd.c (a one-line detection fix for the ALTER
COLUMN error, an error guard for whole-row variables, and rewording
"equijoin" to "equality join"). Other than that, there are no major
changes in v5 compared to v2-v4. At this stage I'd really appreciate
feedback on the overall design approach.

Best,
Alex

-- 
Alexandra Wang
EDB: https://www.enterprisedb.com