| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Christian Ullrich <chris(at)chrullrich(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL in Windows console and Ctrl-C |
| Date: | 2014-04-14 22:51:23 |
| Message-ID: | 20140414225123.GA9072@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Apr 14, 2014 at 09:34:14AM +0530, Amit Kapila wrote:
> The problem can be solved this way, but the only question here is whether
> it is acceptable for users to have a new console window for server.
>
> Can others also please share their opinion if this fix (start server in new
> console) seems acceptable or shall we try by passing some information
> from pg_ctl and then ignore CTRL+C && CTRL+BREAK for it?
I wanted to point out that I think this patch is only appropriate for
head, not backpatching. Also, on Unix we have to handle signals that
come from the kill command. Can you send CTRL+C from other
applications on Windows?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2014-04-14 22:51:41 | Re: Excessive WAL generation and related performance issue |
| Previous Message | Jim Nasby | 2014-04-14 22:39:02 | Re: Signaling of waiting for a cleanup lock? |