Re: v10 pg_ctl compatibility

On 2017-09-26 15:15:39 -0700, Jeff Janes wrote:
> On Tue, Sep 26, 2017 at 1:10 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> > Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
> > > To add insult to injury, when v10 pg_ctl does restart a pre-10 server and
> > > it sits there for a long time waiting for it to start up even though it
> > has
> > > already started up, if I hit ctrl-C because I assume something is
> > horribly
> > > wrong, it then goes ahead and kills the successfully started-and-running
> > > server.
> >
> > Really? The server should have detached itself from your terminal
> > group long before that. What platform is this?
> >
>
>
> CentOS release 6.9 (Final)
>
> The sever log file (9.6) says:
>
>
> 64926 2017-09-26 13:56:38.284 PDT LOG: database system was shut down
> at 2017-09-26 13:56:37 PDT
> 64926 2017-09-26 13:56:38.299 PDT LOG: MultiXact member wraparound
> protections are now enabled
> 64930 2017-09-26 13:56:38.311 PDT LOG: autovacuum launcher started
> 64924 2017-09-26 13:56:38.313 PDT LOG: database system is ready to
> accept connections
> ... hit ctrl-C
> 64924 2017-09-26 13:56:47.237 PDT LOG: received fast shutdown request
> 64924 2017-09-26 13:56:47.237 PDT LOG: aborting any active transactions
> 64930 2017-09-26 13:56:47.244 PDT LOG: autovacuum launcher shutting
> down
> 64927 2017-09-26 13:56:47.261 PDT LOG: shutting down
> ...

It's reproducible here. Postmaster never calls setsid() for itself, nor
does pg_ctl for it, therefore ctrl-c's SIGTERM to pg_ctl also go to its
children, namely postmaster.

Greetings,

Andres Freund