From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: v10 pg_ctl compatibility |
Date: | 2017-09-26 23:01:06 |
Message-ID: | 20170926230106.pzeqsipkbfxfms27@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2017-09-26 18:54:17 -0400, Tom Lane wrote:
> Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
> > On Tue, Sep 26, 2017 at 1:10 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2017-09-26 23:05:46 | Re: v10 pg_ctl compatibility |
Previous Message | Tom Lane | 2017-09-26 22:54:17 | Re: v10 pg_ctl compatibility |