Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h2KwS-0006Te-2L for pgsql-admin@arkaria.postgresql.org; Fri, 08 Mar 2019 19:14:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h2KwQ-0004UY-PF for pgsql-admin@arkaria.postgresql.org; Fri, 08 Mar 2019 19:13:58 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h2KwQ-0004Sg-EC for pgsql-admin@lists.postgresql.org; Fri, 08 Mar 2019 19:13:58 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h2KwN-0002YA-Tu for pgsql-admin@postgresql.org; Fri, 08 Mar 2019 19:13:57 +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 x28JDPpZ022602; Fri, 8 Mar 2019 14:13:25 -0500 From: Tom Lane To: Alvaro Herrera cc: Peter , Andrew Gierth , pgsql-admin@postgresql.org, pgsql@FreeBSD.org Subject: Re: Upgrade 10.5->10.6 : db crash BUS ERROR (sig 10), reproducible In-reply-to: <20190308185001.GA14936@alvherre.pgsql> References: <20190308185001.GA14936@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Fri, 08 Mar 2019 15:50:01 -0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <22600.1552072405.1@sss.pgh.pa.us> Date: Fri, 08 Mar 2019 14:13:25 -0500 Message-ID: <22601.1552072405@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Alvaro Herrera writes: > On 2019-Mar-08, Peter wrote: >> On Fri, Mar 08, 2019 at 02:35:33AM +0000, Andrew Gierth wrote: >>> ! I'm pretty sure nothing in our buildfarm is i386 without SSE2 though. >> *laugh* no problem with that. There probably wouldn't be any reason >> to have such. > Actually there *is* a very good reason to have one, which is that we > would have discovered this bug right away. (Just ask Tom Lane for a > tally of bugs that have been discovered due to his old HPUX 10.20 > dinosaur he keeps running just for that purpose). It seems difficult to > grab hold of such hardware, however. I don't suppose you have many > spare cycles on that machine of yours to run a buildfarm animal? IIUC, this bug isn't actually down to the old hardware: any SSE-capable chip ought to exhibit the same problem. The bug is in the toolchain somewhere, in that some compiler or run-time infrastructure is failing to maintain 16-byte stack alignment as required by the ABI. Or, possibly, there is disagreement among relevant toolchain elements as to exactly what ABI they're using. regards, tom lane