Re: Shutting down server from a backend process, e.g. walrceiver

From: fazool mein <fazoolmein(at)gmail(dot)com>
To: David Fetter <david(at)fetter(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Shutting down server from a backend process, e.g. walrceiver
Date: 2010-09-21 17:53:24
Message-ID: AANLkTimnjiOyrGbruNiVmUihcRAyR3LfwskwUESrT6UR@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 21, 2010 at 8:32 AM, David Fetter <david(at)fetter(dot)org> wrote:

> On Mon, Sep 20, 2010 at 05:48:40PM -0700, fazool mein wrote:
> > Hi,
> >
> > I want to shut down the server under certain conditions that can be
> > checked inside a backend process. For instance, while running
> > symmetric
>
> Synchronous?
>

I meant streaming :), but the question is in general for any process forked
by the postmaster.

>
> > 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?
>
> Perhaps I've misunderstood, but since there's already Something
> 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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-09-21 17:56:03 Re: What happened to the is_<type> family of functions proposal?
Previous Message fazool mein 2010-09-21 17:50:56 Re: Shutting down server from a backend process, e.g. walrceiver