From: David Johnston <polobo@yahoo.com>
To: pgsql-hackers@postgresql.org
Subject: Re: Weaker shmem interlock w/o postmaster.pid
Date: Wed, 11 Sep 2013 19:57:22 -0700 (PDT)
Message-ID: <1378954642417-5770559.post@n5.nabble.com> (raw)
In-Reply-To: <20130912022800.GB260242@tornado.leadboat.com>
References: <20130911033341.GD225735@tornado.leadboat.com>
<20130911153200.GD2706@tamriel.snowman.net>
<20130912022800.GB260242@tornado.leadboat.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
Noah Misch-2 wrote
>> > I'm thinking to preserve postmaster.pid at immediate shutdown in all
>> released
>> > versions, but I'm less sure about back-patching a change to make
>> > PGSharedMemoryCreate() pickier. On the one hand, allowing startup to
>> proceed
>> > with backends still active in the same data directory is a corruption
>> hazard.
>>
>> The corruption risk, imv anyway, is sufficient to backpatch the change
>> and overrides the concerns around very fast shutdown/restarts.
>
> Making PGSharedMemoryCreate() pickier in all branches will greatly
> diminish
> the marginal value of preserving postmaster.pid, so I'm fine with dropping
> the
> postmaster.pid side of the proposal.
Its probably still worth a fresh look at the immediate shutdown process to
see whether the current location where postmaster.pid is removed is
acceptable. It may not be necessary to leave it in place always but:
1) if there is a section of shared memory that can only be reached/found if
one knows the pid, and
2) postmaster.pid is removed before that area is "secured from future
clobbering"
then there may be a risk that can still be mitigated by moving its removal
without having to go to the extreme.
David J.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Weaker-shmem-interlock-w-o-postmaster-pid-tp5770399p5770559....
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
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: polobo@yahoo.com
Subject: Re: Weaker shmem interlock w/o postmaster.pid
In-Reply-To: <1378954642417-5770559.post@n5.nabble.com>
* 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