Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZFqVm-00035l-2P for pgsql-admin@arkaria.postgresql.org; Thu, 16 Jul 2015 21:16:10 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZFqVl-0001Fd-EV for pgsql-admin@arkaria.postgresql.org; Thu, 16 Jul 2015 21:16:09 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZFqUA-0007mq-GR for pgsql-admin@postgresql.org; Thu, 16 Jul 2015 21:14:30 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZFqU8-0007Gl-9n for pgsql-admin@postgresql.org; Thu, 16 Jul 2015 21:14:29 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id t6GLEQNt009257; Thu, 16 Jul 2015 17:14:26 -0400 From: Tom Lane To: Yiqing Jin cc: pgsql-admin@postgresql.org Subject: Re: segfault when creating index on huge table In-reply-to: References: Comments: In-reply-to Yiqing Jin message dated "Thu, 16 Jul 2015 10:29:27 -0700" Date: Thu, 16 Jul 2015 17:14:26 -0400 Message-ID: <9256.1437081266@sss.pgh.pa.us> X-Pg-Spam-Score: -3.2 (---) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Yiqing Jin 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