Re: Ctrl+C from sh can shut down daemonized PostgreSQL cluster - Mailing list pgsql-hackers

From Bjorn Munch
Subject Re: Ctrl+C from sh can shut down daemonized PostgreSQL cluster
Date
Msg-id 20140217093829.GA1045@khepri15.no.oracle.com
Whole thread Raw
In response to Ctrl+C from sh can shut down daemonized PostgreSQL cluster  (Kevin Grittner <kgrittn@ymail.com>)
Responses Re: Ctrl+C from sh can shut down daemonized PostgreSQL cluster  (Bruce Momjian <bruce@momjian.us>)
Re: Ctrl+C from sh can shut down daemonized PostgreSQL cluster  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On 14/02 14.57, Kevin Grittner wrote:
> We have had a case where a production cluster was accidentally shut
> down by a customer who used Ctrl+C in the same sh session in which
> they had (long before) run pg_ctl start.  We have only seen this in
> sh on Solaris.  Other shells on Solaris don't behave this way, nor
> does sh on tested versions of Linux.  Nevertheless, the problem is
> seen on the default shell for a supported OS.

What Solaris version, and what version of sh?  sh on Solaris isn't
necessarily the "real" bourne shell. In Solaris 11 it's actually
ksh93.

I've seen a sort-of opposite problem which does not appear in stock
Solaris 10 or 11 but in OpenSolaris, at least the version I used to
have on my desktop.

And this was not PostgreSQL but MySQL.... There's a script mysqld_safe
which will automatically restart the mysqld server if it dies. But in
OpenSolaris with ksh version '93t', if I killed mysqld, the shell that
started it also died. I never could figure out why. Solaris 11 with
ksh '93u' does not have this problem. Nor does Solaris 10 with "real" sh.

Is this customer by any chance running OpenSolaris?

- Bjorn



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: CREATE FOREIGN TABLE ( ... LIKE ... )
Next
From: Christian Kruse
Date:
Subject: Re: Patch: show xid and xmin in pg_stat_activity and pg_stat_replication