From: Tom Lane <tgl@sss.pgh.pa.us>
To: Yiqing Jin <yiqing.jin@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: segfault when creating index on huge table
Date: Thu, 16 Jul 2015 17:14:26 -0400
Message-ID: <9256.1437081266@sss.pgh.pa.us> (raw)
In-Reply-To: <CAL8HZuNR2FR1owZHWG-p64GJtNfbbmPx1Y2OXmJ_XuQ3P8YtVA@mail.gmail.com>
References: <CAL8HZuNR2FR1owZHWG-p64GJtNfbbmPx1Y2OXmJ_XuQ3P8YtVA@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
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: tgl@sss.pgh.pa.us, yiqing.jin@gmail.com
Subject: Re: segfault when creating index on huge table
In-Reply-To: <9256.1437081266@sss.pgh.pa.us>
* 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