Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZFu3q-0002Mm-65 for pgsql-admin@arkaria.postgresql.org; Fri, 17 Jul 2015 01:03:34 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZFu3p-0000hl-Av for pgsql-admin@arkaria.postgresql.org; Fri, 17 Jul 2015 01:03:33 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZFu3n-0000hT-Nc for pgsql-admin@postgresql.org; Fri, 17 Jul 2015 01:03:31 +0000 Received: from mail-pa0-x233.google.com ([2607:f8b0:400e:c03::233]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1ZFu3g-0003sg-9M for pgsql-admin@postgresql.org; Fri, 17 Jul 2015 01:03:31 +0000 Received: by pactm7 with SMTP id tm7so51741787pac.2 for ; Thu, 16 Jul 2015 18:03:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=bFeg2uvBLthIs8mIp8itQEGNa9M51B6mZWkzKZng4+w=; b=SfnntOW7XADZq9Zm0OxYU/GbxRmxpL2r8OV+xV+AwakfebApGr/Kt8f61Azyk0LH6y ZMUy9ioWeX/6qp/1XFzsS3hmCXDK9dbImbJ5usqY+hB/x4QfuLBwltsAL2ZJsOpzvbpF Ofq0GKlg1zTyryEJZEsvkX2AAsAs5X8WVakVyY15ps0D5lbAmpH8z1b+gOhktHygFcs6 aiHUcGy1hk5wqlziyHnCZ/bg8VX6HVMtxmertWAwgYFUN28lvYA2/6MR2bnmiN+3EPHi i+hMOJJcfY56nKgt8DPC+6abflETeT7CdYQl4fGOY/p1j5kDLFMh7MRoaxttpC4W5jz/ HWRw== X-Received: by 10.70.133.170 with SMTP id pd10mr24019086pdb.127.1437095000853; Thu, 16 Jul 2015 18:03:20 -0700 (PDT) Received: from ?IPv6:2620:149:5:1b05:f406:b5b:49c3:3b97? ([2620:149:5:1b05:f406:b5b:49c3:3b97]) by smtp.gmail.com with ESMTPSA id dm1sm9199789pbb.35.2015.07.16.18.03.19 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 16 Jul 2015 18:03:20 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\)) Subject: Re: segfault when creating index on huge table From: Yiqing Jin In-Reply-To: <9256.1437081266@sss.pgh.pa.us> Date: Thu, 16 Jul 2015 18:03:19 -0700 Cc: pgsql-admin@postgresql.org Content-Transfer-Encoding: 7bit Message-Id: <4D1580D9-D560-45B2-8BA2-97058B6F8D85@gmail.com> References: <9256.1437081266@sss.pgh.pa.us> To: Tom Lane X-Mailer: Apple Mail (2.2102) X-Pg-Spam-Score: -2.0 (--) 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 Yes it finished successfully after changing it to 50G! Thanks Tom! > On Jul 16, 2015, at 2:14 PM, Tom Lane wrote: > > 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