| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| 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 09:45:31 |
| Message-ID: | 4A8BC9BB.1010109@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
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).
Is pg_standby killed correctly when postmaster dies?
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-08-19 14:43:16 | Re: BUG #4993: memory issue with array_agg |
| Previous Message | Gaurav K Srivastav | 2009-08-19 09:45:05 | Regarding permissions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-08-19 11:14:52 | alpha1 bundled -- please verify |
| Previous Message | Magnus Hagander | 2009-08-19 09:30:26 | Re: BUG #4961: pg_standby.exe crashes with no args |