Include chunk overhead in hash table entry size estimate.
authorJeff Davis <jdavis@postgresql.org>
Sat, 4 Apr 2020 02:52:16 +0000 (19:52 -0700)
committerJeff Davis <jdavis@postgresql.org>
Sat, 4 Apr 2020 03:07:58 +0000 (20:07 -0700)
commit0588ee63aa2d8c5765d086991555cd9acdd4d86f
tree6992318ae8adc1e241c73f063b55f61203daa136
parent3e0d80fd8d3dd4f999e0d3aa3e591f480d8ad1fd
Include chunk overhead in hash table entry size estimate.

Don't try to be precise about it, just use a constant 16 bytes of
chunk overhead. Being smarter would require knowing the memory context
where the chunk will be allocated, which is not known by all callers.

Discussion: https://postgr.es/m/20200325220936.il3ni2fj2j2b45y5@alap3.anarazel.de
src/backend/executor/nodeAgg.c
src/include/executor/nodeAgg.h