Re: Ctrl+C from sh can shut down daemonized PostgreSQL cluster

From: Hannu Krosing <hannu(at)2ndQuadrant(dot)com>
To: Greg Stark <stark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Kevin Grittner <kgrittn(at)ymail(dot)com>
Subject: Re: Ctrl+C from sh can shut down daemonized PostgreSQL cluster
Date: 2014-02-15 11:02:41
Message-ID: 52FF4951.1030408@2ndQuadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 02/15/2014 02:25 AM, Greg Stark wrote:
>
>
> On 14 Feb 2014 23:07, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us
> <mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us>> wrote:
> >
> > If this is, as it sounds to be, a Solaris shell bug, doesn't it
> > affect other daemons too?
>
> This is simmering i never exactly followed but i think if the shell
> doesn't support job control it's expected behaviour, not a bug. Only
> shells that support job control create new process groups for every
> backgrounded command.
>
> I would have expected if I run postgres myself that it be attached to
> the terminal and die when I C-c it but if it's started by pg_ctl I
> would have thought it was running independently of my terminal and shell.
>
In this case maybe it is pg_ctl which should do the deamoinizing ?

Cheers

--
Hannu Krosing
PostgreSQL Consultant
Performance, Scalability and High Availability
2ndQuadrant Nordic OÜ

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-02-15 11:11:03 Re: Memory ordering issue in LWLockRelease, WakeupWaiters, WALInsertSlotRelease
Previous Message Hiroshi Inoue 2014-02-15 10:56:22 Re: narwhal and PGDLLIMPORT