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

From David G. Johnston
Subject Re: BUG #18958: "pg_ctl start" allows subsequent CTRL-C key in cmd.exe to unexpectedly terminate cluster on Windows
Date
Msg-id CAKFQuwYFqPRwH6WADXo5UtuwuoSYDaZe6ubrC6=Y8hgD4bMU=A@mail.gmail.com
Whole thread Raw
List pgsql-bugs
On Fri, Jun 13, 2025 at 12:50 PM Seva Zaslavsky <szaslavsky@mpcapitallp.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.

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table.
Next
From: Tom Lane
Date:
Subject: Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17