Re: PostgreSQL in Windows console and Ctrl-C

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Christian Ullrich <chris(at)chrullrich(dot)net>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PostgreSQL in Windows console and Ctrl-C
Date: 2014-04-15 03:10:10
Message-ID: CAA4eK1Ju5eVPaGqUeeGWABRGEB4tvvNPHJ_5hdXAxr-oWZdEdA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 14, 2014 at 11:46 AM, Christian Ullrich
<chris(at)chrullrich(dot)net> wrote:
> * From: Amit Kapila
>> Do you mean to say use some existing environment variable?
>> Introducing an environment variable to solve this issue or infact using
>> some existing environ variable doesn't seem to be the best way to pass
>> such information.
>
> I meant creating a new one, yes. If, say, PGSQL_BACKGROUND_JOB was set,
> the postmaster etc. would ignore the events.

Do you plan to reset it and if yes when?
I think there is chance that after setting this environment variable, some other
instance of server (postmaster) can read it and missed the signal
which it should
have otherwise processed.

Irrespective of above problem, I think using environment variable might not be a
good way to solve this problem.

With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2014-04-15 04:06:44 Re: PostgreSQL in Windows console and Ctrl-C
Previous Message Andrew Dunstan 2014-04-15 03:07:31 Re: [COMMITTERS] pgsql: Add TAP tests for client programs