Re: segfault when creating index on huge table

Yes it finished successfully after changing it to 50G!

Thanks Tom!

> On Jul 16, 2015, at 2:14 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Yiqing Jin <yiqing.jin@gmail.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