From: | Christian Ullrich <chris(at)chrullrich(dot)net> |
---|---|
To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Subject: | Re: PostgreSQL in Windows console and Ctrl-C |
Date: | 2014-04-15 18:23:50 |
Message-ID: | a6e5ae73b5c943f1b5d202c05c36b1aa@AMSPR06MB134.eurprd06.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* From: Robert Haas
> On Mon, Apr 14, 2014 at 2:16 AM, Christian Ullrich
> <chris(at)chrullrich(dot)net> wrote:
> > I meant creating a new one, yes. If, say, PGSQL_BACKGROUND_JOB was
> > set, the postmaster etc. would ignore the events.
>
> Why not just pass a command-line switch?
Because, as I wrote in the message you are quoting, I did not think that
having a command-line option for the sole purpose of telling the
postmaster who its parent is was a suitable solution.
I had already given up on that idea based on Amit's advice, and I will
create a patch based on a command-line option.
While I have you here, though, any suggestions on what the name of that
option should be? I think --background is about right. Also, how should
I treat the option on non-Windows platforms? Should it just not be there
(= error), or be ignored if present?
--
Christian
From | Date | Subject | |
---|---|---|---|
Next Message | Christian Ullrich | 2014-04-15 18:29:34 | Re: PostgreSQL in Windows console and Ctrl-C |
Previous Message | Peter Geoghegan | 2014-04-15 18:15:44 | Re: Clock sweep not caching enough B-Tree leaf pages? |