diff options
author | Noah Misch <noah@leadboat.com> | 2013-06-27 14:53:57 -0400 |
---|---|---|
committer | Noah Misch <noah@leadboat.com> | 2013-06-27 14:53:57 -0400 |
commit | 263865a48973767ce8ed7b7788059a38a24a9f37 (patch) | |
tree | 282d6522ada24adc923ea869c01b9d94f02685db /src/backend/tcop/postgres.c | |
parent | 9ef86cd994e9f2a684996df994d4657e84a6c0bb (diff) | |
download | postgresql-263865a48973767ce8ed7b7788059a38a24a9f37.tar.gz postgresql-263865a48973767ce8ed7b7788059a38a24a9f37.zip |
Permit super-MaxAllocSize allocations with MemoryContextAllocHuge().
The MaxAllocSize guard is convenient for most callers, because it
reduces the need for careful attention to overflow, data type selection,
and the SET_VARSIZE() limit. A handful of callers are happy to navigate
those hazards in exchange for the ability to allocate a larger chunk.
Introduce MemoryContextAllocHuge() and repalloc_huge(). Use this in
tuplesort.c and tuplestore.c, enabling internal sorts of up to INT_MAX
tuples, a factor-of-48 increase. In particular, B-tree index builds can
now benefit from much-larger maintenance_work_mem settings.
Reviewed by Stephen Frost, Simon Riggs and Jeff Janes.
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions