From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Baker, Keith [OCDUS Non-J&J]" <KBaker9(at)its(dot)jnj(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal to add a QNX 6.5 port to PostgreSQL |
Date: | 2014-08-05 00:15:31 |
Message-ID: | 53E02223.7080605@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 08/04/2014 07:54 AM, Robert Haas wrote:
> 1. Most seriously, once the postmaster is gone, there's nobody to
> SIGQUIT remaining backends if somebody exits uncleanly. This means
> that a backend running without a postmaster could be running in a
> corrupt shared memory segment, which could lead to all sorts of
> misbehavior, including possible data corruption.
I've seen this in the field.
> 2. Operationally, orphaned backends prevent the system from being
> restarted. There's no easy, automatic way to kill them, so scripts
> that automatically restart the database server if it exits don't work.
I've also seen this in the field.
> Now, I don't say that any of this is a reason not to have a strong
> shared memory interlock, but I'm quite unconvinced that the current
> behavior should even be optional, let alone the default.
I always assumed that the current behavior existed because we *couldn't*
fix it, not because anybody wanted it.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2014-08-05 02:41:02 | Re: wrapping in extended mode doesn't work well with default pager |
Previous Message | John Cochran | 2014-08-04 21:40:06 | Re: Looked at TODO:Considering improving performance of computing CHAR() value lengths |