Re: segfault when creating index on huge table

From: Yiqing Jin <yiqing(dot)jin(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: segfault when creating index on huge table
Date: 2015-07-17 01:03:19
Message-ID: 4D1580D9-D560-45B2-8BA2-97058B6F8D85@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Yes it finished successfully after changing it to 50G!

Thanks Tom!

> On Jul 16, 2015, at 2:14 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Yiqing Jin <yiqing(dot)jin(at)gmail(dot)com> writes:
>> maintenance_work_mem = 128000MB
>
> Just a thought ... does the crash go away if you reduce that to something
> like 50GB? It suddenly strikes me that qsort_tuple is not being careful
> about size_t being wider than int.
>
> regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2015-07-17 03:16:11 Re: segfault when creating index on huge table
Previous Message Tom Lane 2015-07-16 21:14:26 Re: segfault when creating index on huge table