Re: PostgreSQL in Windows console and Ctrl-C - Mailing list pgsql-hackers

From Christian Ullrich
Subject Re: PostgreSQL in Windows console and Ctrl-C
Date
Msg-id a6e5ae73b5c943f1b5d202c05c36b1aa@AMSPR06MB134.eurprd06.prod.outlook.com
Whole thread Raw
In response to Re: PostgreSQL in Windows console and Ctrl-C  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: PostgreSQL in Windows console and Ctrl-C  (Amit Kapila <amit.kapila16@gmail.com>)
Re: PostgreSQL in Windows console and Ctrl-C  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
* From: Robert Haas

> On Mon, Apr 14, 2014 at 2:16 AM, Christian Ullrich
> <chris@chrullrich.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



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Clock sweep not caching enough B-Tree leaf pages?
Next
From: Christian Ullrich
Date:
Subject: Re: PostgreSQL in Windows console and Ctrl-C