From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, wader2 <wader2(at)jcom(dot)home(dot)ne(dot)jp>, pgsql-bugs(at)postgresql(dot)org, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: BUG #4961: pg_standby.exe crashes with no args |
Date: | 2009-08-19 19:56:50 |
Message-ID: | 9837222c0908191256j24981969o6647b5abe3fd85ad@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Wed, Aug 19, 2009 at 11:45, Heikki
Linnakangas<heikki(dot)linnakangas(at)enterprisedb(dot)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 Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2009-08-19 20:32:21 | Re: fillfactor hides autovacuum parameters in 8.4.0 |
Previous Message | Shivesh Wangrungvichaisri | 2009-08-19 15:50:44 | BUG #4996: postgres.exe memory consumption keeps going up |
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2009-08-19 20:09:08 | Re: We should Axe /contrib/start-scripts |
Previous Message | Tom Lane | 2009-08-19 19:06:09 | Re: We should Axe /contrib/start-scripts |