Re: [BUGS] BUG #4961: pg_standby.exe crashes with no args - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: [BUGS] BUG #4961: pg_standby.exe crashes with no args
Date
Msg-id 9837222c0908191256j24981969o6647b5abe3fd85ad@mail.gmail.com
Whole thread Raw
In response to Re: [BUGS] BUG #4961: pg_standby.exe crashes with no args  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Wed, Aug 19, 2009 at 11:45, Heikki
Linnakangas<heikki.linnakangas@enterprisedb.com> wrote:
> Magnus Hagander wrote:
>> This would amount to fairly major surgery for pg_standby on Win32. Is
>> that something we'd want to backpatch, or do we want to backpatch just
>> the removal of the signal() calls which would amount to not supporting
>> signals in pg_standby on win32?
>
> I think we should just remove the signals support for win32. The trigger
> file method still works, and the signal method has always been a bit
> iffy (it doesn't work when pg_standby isn't running, for example, which
> happens between processing of each WAL file, because there's no process
> to signal).

Fair enough.


> Is pg_standby killed correctly when postmaster dies?

No idea. I can set up and env to test, but I don't have one ready.
Anybody else have tried this?

-- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: We should Axe /contrib/start-scripts
Next
From: "Kevin Grittner"
Date:
Subject: Re: We should Axe /contrib/start-scripts