From: Yiqing Jin <yiqing.jin@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: segfault when creating index on huge table
Date: Thu, 16 Jul 2015 18:03:19 -0700
Message-ID: <4D1580D9-D560-45B2-8BA2-97058B6F8D85@gmail.com> (raw)
In-Reply-To: <9256.1437081266@sss.pgh.pa.us>
References: <CAL8HZuNR2FR1owZHWG-p64GJtNfbbmPx1Y2OXmJ_XuQ3P8YtVA@mail.gmail.com>
<9256.1437081266@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
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
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: yiqing.jin@gmail.com, tgl@sss.pgh.pa.us
Subject: Re: segfault when creating index on huge table
In-Reply-To: <4D1580D9-D560-45B2-8BA2-97058B6F8D85@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox