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

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: skoposov(at)cmu(dot)edu
Cc: PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14722: Segfault in tuplesort_heap_siftup, 32 bit overflow
Date: 2017-06-29 16:34:40
Message-ID: CAH2-Wzmdygq8tSN+qKtG+QFeRSzSLj2byT_oNqVOjzJN4+1H6Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Jun 29, 2017 at 9:16 AM, <skoposov(at)cmu(dot)edu> wrote:
> I have a very large table (40e9 records) that I'm trying to create the index
> on and I am getting a segmentation fault that could be traced as far as I
> understand to a 32 bit int overflow in tuplesort_heap_siftup

Can your print the Tuplesortstate (the variable "state") within GDB,
and post it here?

--
Peter Geoghegan

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Sergey Koposov 2017-06-29 16:50:31 Re: BUG #14722: Segfault in tuplesort_heap_siftup, 32 bit overflow
Previous Message skoposov 2017-06-29 16:16:37 BUG #14722: Segfault in tuplesort_heap_siftup, 32 bit overflow