Re: BUG #7885: postmaster panic on startup does not release shared memory

From: David Thomas <david(dot)thomas(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #7885: postmaster panic on startup does not release shared memory
Date: 2013-02-15 23:07:20
Message-ID: 20130215230719.GA17308@digitaldogma.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Feb 15, 2013 at 05:02:46PM -0500, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Daniel Farina 2013-02-15 23:15:16 Re: BUG #7883: "PANIC: WAL contains references to invalid pages" on replica recovery
Previous Message Tom Lane 2013-02-15 22:14:53 Re: BUG #7886: date_trunc(date) returning timestamptz instead of timestamp