Re: BUG #7885: postmaster panic on startup does not release shared memory - Mailing list pgsql-bugs

From David Thomas
Subject Re: BUG #7885: postmaster panic on startup does not release shared memory
Date
Msg-id 20130215230719.GA17308@digitaldogma.org
Whole thread Raw
In response to Re: BUG #7885: postmaster panic on startup does not release shared memory  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Fri, Feb 15, 2013 at 05:02:46PM -0500, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > When we panic, we PANIC, meaning we don't jump around looking for
> > cleanup stuff, which might make things worse.
>
> I think also there was some thought that we should intentionally leave
> the shmem segment around for debugging purposes.
>
> In any case, I believe the behavior complained of here is specific to
> --single mode, which is surely not a production scenario, thus even
> less reason to be concerned about it.  (If a postmaster child panics,
> the postmaster will still shut down normally and thus release the
> shmem segment.)
>
Yup, if I attempt to start the cluster normally, it cleans up after
itself, so this is specific to --single mode.

--
David Thomas
System Engineer
EnterpriseDB - The Enterprise PostgreSQL Company

pgsql-bugs by date:

Previous
From: Daniel Farina
Date:
Subject: Re: BUG #7883: "PANIC: WAL contains references to invalid pages" on replica recovery
Next
From: Maciek Sakrejda
Date:
Subject: Re: BUG #7883: "PANIC: WAL contains references to invalid pages" on replica recovery