On Thu, Dec 8, 2016 at 12:20 AM, Heikki Linnakangas <heikki.linnakan...@iki.fi> wrote: > While we're at it, add a safeguard for the case that we are already over > the limit when allocating the read buffers. That shouldn't happen, but > better safe than sorry.
I think you should 's/Min/Max/' where the new limit is applied. Also suggest that the subsequent USEMEM() call have "state->read_buffer_size * numInputTapes" as its argument, rather than state->availMem, just to be neat. Thanks -- Peter Geoghegan -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
