Hi,
On Mon, Sep 21, 2009 at 1:55 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
The startup process could capture stderr from walreceiver and forward it
with elog(LOG).
The startup process should obtain also the message level in some way
(pipe?), and control the messages
Fujii Masao wrote:
On Fri, Sep 18, 2009 at 7:34 PM, Fujii Masao masao.fu...@gmail.com wrote:
This approach is OK if the stand-alone walreceiver is treated steadily
by the startup process like a child process under postmaster:
* Handling of some interrupts: SIGHUP, SIGTERM?, SIGINT, SIGQUIT...
Hi,
On Fri, Sep 18, 2009 at 7:34 PM, Fujii Masao masao.fu...@gmail.com wrote:
This approach is OK if the stand-alone walreceiver is treated steadily
by the startup process like a child process under postmaster:
* Handling of some interrupts: SIGHUP, SIGTERM?, SIGINT, SIGQUIT...
For
