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

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Sergey Koposov <skoposov(at)cmu(dot)edu>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14722: Segfault in tuplesort_heap_siftup, 32 bit overflow
Date: 2017-07-12 17:44:33
Message-ID: CAH2-WzmhsMPfONa2fuWppsPtDuNJMDw7yO6M79RJG1bxKx6MgQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Jul 12, 2017 at 10:42 AM, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
>> FWIW, memtupcount is allowed to go negative.
>
>
> Huh, say what?

Well, there are defenses against that case, both in assertions and in
code like tuplesort_heap_delete_top(). In that sense, it's allowed to
go negative.

--
Peter Geoghegan

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2017-07-12 19:09:23 Re: BUG #14654: With high statistics targets on ts_vector, unexpectedly high memory use & OOM are triggered
Previous Message Heikki Linnakangas 2017-07-12 17:42:55 Re: BUG #14722: Segfault in tuplesort_heap_siftup, 32 bit overflow