Re: Shutting down server from a backend process, e.g. walrceiver
От | fazool mein |
---|---|
Тема | Re: Shutting down server from a backend process, e.g. walrceiver |
Дата | |
Msg-id | AANLkTimnjiOyrGbruNiVmUihcRAyR3LfwskwUESrT6UR@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Shutting down server from a backend process, e.g. walrceiver (David Fetter <david@fetter.org>) |
Список | pgsql-hackers |
On Tue, Sep 21, 2010 at 8:32 AM, David Fetter <david@fetter.org> wrote:
I meant streaming :), but the question is in general for any process forked by the postmaster.
(wondering)
Thanks.
On Mon, Sep 20, 2010 at 05:48:40PM -0700, fazool mein wrote:Synchronous?
> Hi,
>
> I want to shut down the server under certain conditions that can be
> checked inside a backend process. For instance, while running
> symmetric
I meant streaming :), but the question is in general for any process forked by the postmaster.
Perhaps I've misunderstood, but since there's already Something
> replication, if the primary dies, I want the the walreceiver to
> detect that and shutdown the standby. The reason for shutdown is
> that I want to execute some other stuff before I start the standby
> as a primary. Creating a trigger file doesn't help as it converts
> the standby into primary at run time.
>
> Using proc_exit() inside walreceiver only terminates the walreceiver
> process, which postgres starts again. The other way I see is using
> ereport(PANIC, ...). Is there some other way to shutdown the main
> server from within a backend process?
Else(TM) which takes actions, why not send a message to it so it can
take appropriate action on the node, starting with shutting it down?
(wondering)
Thanks.
В списке pgsql-hackers по дате отправления: