On 2017-09-26 18:54:17 -0400, Tom Lane wrote:
> Jeff Janes <jeff.janes@gmail.com> writes:
> > On Tue, Sep 26, 2017 at 1:10 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >> Really? The server should have detached itself from your terminal
> >> group long before that. What platform is this?
>
> > CentOS release 6.9 (Final)
>
> Hm, same as here. Are you perhaps not using pg_ctl's -l option?
> If not, the postmaster's stderr would remain attached to your tty,
> which might be the reason why a terminal ^C affects it.
Doesn't make a difference here (Debian sid), I see postgres get
SIGTERMed either way. GDBing in and doing a setsid() in postmaster
before ctrl-c'ing pg_ctl "fixes" it. Is there a reason we're not doing
so after the fork in pg_ctl?
Greetings,
Andres Freund
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers