pgsql: Trim ORDER BY/DISTINCT aggregate pathkeys in gather_grouping_pat

2024-03-14 Thread David Rowley
Trim ORDER BY/DISTINCT aggregate pathkeys in gather_grouping_paths

Similar to d8a295389, trim off any PathKeys which are for ORDER BY /
DISTINCT aggregate functions from the PathKey List for the Gather Merge
paths created by gather_grouping_paths().  These additional PathKeys are
not valid to use after grouping has taken place as these PathKeys belong
to columns which are inputs to an aggregate function and, therefore are
unavailable after aggregation.

Reported-by: Alexander Lakhin
Discussion: https://postgr.es/m/cf63174c-8c89-3953-cb49-48f41f749...@gmail.com
Backpatch-through: 16, where 1349d2790 was added

Branch
--
REL_16_STABLE

Details
---
https://git.postgresql.org/pg/commitdiff/4e1ff2aadefbfbf798a4d318514ac85b2fbdc5aa

Modified Files
--
src/backend/optimizer/plan/planner.c | 27 +++
1 file changed, 19 insertions(+), 8 deletions(-)



pgsql: Trim ORDER BY/DISTINCT aggregate pathkeys in gather_grouping_pat

2024-03-14 Thread David Rowley
Trim ORDER BY/DISTINCT aggregate pathkeys in gather_grouping_paths

Similar to d8a295389, trim off any PathKeys which are for ORDER BY /
DISTINCT aggregate functions from the PathKey List for the Gather Merge
paths created by gather_grouping_paths().  These additional PathKeys are
not valid to use after grouping has taken place as these PathKeys belong
to columns which are inputs to an aggregate function and, therefore are
unavailable after aggregation.

Reported-by: Alexander Lakhin
Discussion: https://postgr.es/m/cf63174c-8c89-3953-cb49-48f41f749...@gmail.com
Backpatch-through: 16, where 1349d2790 was added

Branch
--
master

Details
---
https://git.postgresql.org/pg/commitdiff/4169850f0b6fc98a5f28d2b0ca4c3a4c1ecf4553

Modified Files
--
src/backend/optimizer/plan/planner.c | 19 +++
1 file changed, 15 insertions(+), 4 deletions(-)