Re: BUG #18958: "pg_ctl start" allows subsequent CTRL-C key in cmd.exe to unexpectedly terminate cluster on Windows

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Seva Zaslavsky <szaslavsky(at)mpcapitallp(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18958: "pg_ctl start" allows subsequent CTRL-C key in cmd.exe to unexpectedly terminate cluster on Windows
Date: 2025-06-13 20:04:38
Message-ID: CAKFQuwYFqPRwH6WADXo5UtuwuoSYDaZe6ubrC6=Y8hgD4bMU=A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Jun 13, 2025 at 12:50 PM Seva Zaslavsky <szaslavsky(at)mpcapitallp(dot)com>
wrote:

> I'm still observing the behavior that pressing CTRL-C inside cmd.exe
> terminates the cluster that was started inside that cmd.exe.
>
> According to the documentation for pg_ctl "The server is started in the
> background, and its standard input is attached to /dev/null (or nul on
> Windows)." but if pressing CTRL-C in a cmd.exe window terminates the
> cluster that was started inside that cmd.exe window, doesn't it seem like
> stdin is attached to the output cmd.exe and not to NUL?
>
ctrl-c sends an operating system signal. Signals don't use
stdin/stdout/etc... to communicate

David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2025-06-13 20:58:44 Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references
Previous Message Seva Zaslavsky 2025-06-13 19:50:11 Re: BUG #18958: "pg_ctl start" allows subsequent CTRL-C key in cmd.exe to unexpectedly terminate cluster on Windows