Re: BUG #14722: Segfault in tuplesort_heap_siftup, 32 bit overflow

On Thu, Jun 29, 2017 at 10:50 AM, Sergey Koposov <skoposov(at)cmu(dot)edu> wrote:
> For the time being I've just changed the type of i,j from int to long
> (or int64) and I am running the index creation now. I let you submit a
> patch -- thanks in advance.

That's more or less what I had in mind.

> I also noticed that the availMem variable was negative in the printout
> of the TupleSortState.
> availMem =-6442450776,
> I don't know whether that's an issue on its own or was caused by the
> (i,j) overflow. (availMem seems to be int64 variable though).

That's definitely allowed to go negative, which is why it's int64.
That's about 6GB of memory, though, which seems unusually large.

--
Peter Geoghegan