Don't use MinMaxAggPath if aggregate's input and output types don't match. A sort-operator option only makes sense for an aggregate that behaves like MIN or MAX. We can't really verify whether an aggregate does, but for our purposes the most important expectation is that the aggregate returns the same type as its input. Without this, the planner's conversion to a MinMaxAggPath plan risks type violations. Since such aggregate definitions might already exist in the wild, check this during planning and don't generate MinMaxAggPath if the types don't match.
Reported-by: Zheng Yu <[email protected]> Author: Tom Lane <[email protected]> Backpatch-through: 14-19 Security: CVE-2026-116331 Branch ------ REL_19_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/75c0441bad98dda75b18cb2b7cf3d8c41e7bc631 Author: Tom Lane <[email protected]> Modified Files -------------- src/backend/optimizer/plan/planagg.c | 17 +++++++++++++++++ 1 file changed, 17 insertions(+)
