Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dwZpJ-00080T-03 for pgsql-hackers@arkaria.postgresql.org; Mon, 25 Sep 2017 20:18:01 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dwZpI-0002yC-He for pgsql-hackers@arkaria.postgresql.org; Mon, 25 Sep 2017 20:18:00 +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_2) (envelope-from ) id 1dwZkk-0007h4-OO for pgsql-hackers@postgresql.org; Mon, 25 Sep 2017 20:13:18 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dwZkg-0006Ui-Bk for pgsql-hackers@postgresql.org; Mon, 25 Sep 2017 20:13:18 +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 v8PKD9eW011340; Mon, 25 Sep 2017 16:13:09 -0400 From: Tom Lane To: Thomas Munro cc: Robert Haas , Andres Freund , amul sul , PostgreSQL-development Subject: Re: Server crash due to SIGBUS(Bus Error) when trying to access the memory created using dsm_create(). In-reply-to: <2034.1506365794@sss.pgh.pa.us> References: <25838.1471010881@sss.pgh.pa.us> <20170628230458.n5ehizmvhoerr5yq@alap3.anarazel.de> <26247.1506349378@sss.pgh.pa.us> <488.1506364109@sss.pgh.pa.us> <2034.1506365794@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Mon, 25 Sep 2017 14:56:34 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <11338.1506370389.1@sss.pgh.pa.us> Date: Mon, 25 Sep 2017 16:13:09 -0400 Message-ID: <11339.1506370389@sss.pgh.pa.us> List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org I wrote: > Rather than dig into the guts of glibc to find that out, though, I think > we should just s/fallocate/posix_fallocate/g on this patch. The argument > for using the former seemed pretty thin to begin with. Pushed with that change; we'll soon see what the buildfarm thinks. I suspect that the provisions for EINTR and ENOSYS errors may now be dead code, since the Linux man page for posix_fallocate mentions neither. They're not much code though, and POSIX itself *does* list EINTR, so I'm hesitant to muck with that. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers