pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: amul sul <sul_amul@yahoo.co.in>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Server crash due to SIGBUS(Bus Error) when trying to access the memory created using dsm_create().
Date: Mon, 25 Sep 2017 14:56:34 -0400
Message-ID: <2034.1506365794@sss.pgh.pa.us> (raw)
In-Reply-To: <488.1506364109@sss.pgh.pa.us>
References: <25838.1471010881@sss.pgh.pa.us>
	<CAEepm=24jFz-Bm6awX-U=qfvcxrbQVS1ZU6uUry07r=aGyePgg@mail.gmail.com>
	<CAEepm=1ySPpiPG8hyy98vTGbvi6uXvavsy-zahevkM=tTRUDSQ@mail.gmail.com>
	<CA+TgmoagA8KGfUZzQs8xMTt2rqjw1Ko+vJQV05R=qZz2a98OGQ@mail.gmail.com>
	<CAEepm=0euOKPaYWz0-gFv9xfG+8ptAjhFjiQEX0CCJaYN--sDQ@mail.gmail.com>
	<CA+TgmoYw296PTpQ+iFqcqWECR5x9QW-TE+Rd5Lv9=p0XCxZvOA@mail.gmail.com>
	<CAEepm=27q=VLg5Mh76a1NfzK=9Xi1jnrpYm5VQNbQQJomwhU4A@mail.gmail.com>
	<CA+TgmoY=jMECqMz=RKG3=x=kvMZrf008Ggc4mYNyajqbVkMW4w@mail.gmail.com>
	<CAEepm=3KjgWXAqseQOXxpz4DtkZJ9U5Zcx9hU8iFrVtm5mwFKg@mail.gmail.com>
	<CAEepm=2GAgjcnLGCHOCVTD04eVR+rP+8_-6Z4c391-AFo1sL7g@mail.gmail.com>
	<20170628230458.n5ehizmvhoerr5yq@alap3.anarazel.de>
	<CAEepm=00bvrcNGaHWv7=9F_SE9YKfW1_DuFbAjFh41ycg8mLxw@mail.gmail.com>
	<CAEepm=37ptJz+epr6+iW+O1wCCAxeT04r27Uc8rXmJBoFT2ExA@mail.gmail.com>
	<CAEepm=3b+Wu81XgseDcc_a6JUC6_JCgyj41LGWfY1qto3gE1KA@mail.gmail.com>
	<26247.1506349378@sss.pgh.pa.us>
	<CA+TgmoY+pXip_OrQdii91iH0UJpL6! Z6NTqQ3ETwBj_Chg8jNrg@mail.gmail.com>
	<488.1506364109@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

I wrote:
> Hmm, so I tested this patch on my RHEL6 box (kernel 2.6.32) and it
> immediately fell over with
> 2017-09-25 14:23:48.410 EDT [325] FATAL:  could not resize shared memory segment "/PostgreSQL.1682054886" to 6928 bytes: Operation not supported
> during startup.  I wonder whether we need to round off the request.

Nope, rounding off doesn't help.  What does help is using posix_fallocate
instead.  I surmise that glibc knows something we don't about how to call
fallocate(2) successfully on this kernel version.

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.

			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



view thread (31+ messages)  latest in thread

Message-ID: <2034.1506365794@sss.pgh.pa.us>
Permalink:  ../2034.1506365794@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2034.1506365794@sss.pgh.pa.us

 · 

reply
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-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, thomas.munro@enterprisedb.com, robertmhaas@gmail.com, andres@anarazel.de, sul_amul@yahoo.co.in
  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>

* 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