pgsql: Guard against possible memory allocation botch in batchmemtuples

Guard against possible memory allocation botch in batchmemtuples().

Negative availMemLessRefund would be problematic. It's not entirely
clear whether the case can be hit in the code as it stands, but this
seems like good future-proofing in any case. While we're at it,
insist that the value be not merely positive but not tiny, so as to
avoid doing a lot of repalloc work for little gain.

Peter Geoghegan

Discussion: <CAM3SWZRVkuUB68DbAkgw=532gW0f+fofKueAMsY7hVYi68MuYQ(at)mail(dot)gmail(dot)com>

Branch
------
REL9_6_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/96ba40c0f15aa1e950b35536387fde30ebbc4547

Modified Files
--------------
src/backend/utils/sort/tuplesort.c | 23 +++++++++++++++++++++--
1 file changed, 21 insertions(+), 2 deletions(-)