Cache catalog lookup data across groups in ordered-set aggregates.
The initial commit of ordered-set aggregates just did all the setup work
afresh each time the aggregate function is started up. But in a GROUP BY
query, the catalog lookups need not be repeated for each group, since the
column datatypes and sort information won't change. When there are many
small groups, this makes for a useful, though not huge, performance
improvement. Per suggestion from Andrew Gierth.
Profiling of these cases suggests that it might be profitable to avoid
duplicate lookups within tuplesort startup as well; but changing the
tuplesort APIs would have much broader impact, so I left that for
another day.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/8b49a6044d06b557047210dba2735081bb037e96
Modified Files
--------------
src/backend/utils/adt/orderedsetaggs.c | 507 ++++++++++++++++++--------------
src/include/catalog/pg_operator.h | 1 +
2 files changed, 290 insertions(+), 218 deletions(-)