Re: the postgres process is not killed when the postmaster is killed

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: 范国腾 <fanguoteng(at)highgo(dot)com>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: the postgres process is not killed when the postmaster is killed
Date: 2018-05-10 09:04:53
Message-ID: 20180510090453.GE26879@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, May 10, 2018 at 08:34:46AM +0000, 范国腾 wrote:
> If the process 2268 is still alive, pg_ctl start and pg_ctl stop will fail.
>
> Is it a bug? What should I configure if I want all of the subprocess are killed?

That's not a bug. On SIGKILL the postmaster does not send down the
message to its subprocesses. Note as well that shared memory is not
released as well, so you may need to kill any extra orphan process
remaining alive after the postmaster is down, so that's not a
recommended way to stop the instance.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2018-05-10 11:18:04 BUG #15192: Implement option to use columns order defined at CSV
Previous Message 范国腾 2018-05-10 08:34:46 the postgres process is not killed when the postmaster is killed