Re: PITR Signalling the Archiver

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Subject: Re: PITR Signalling the Archiver
Date: 2004-05-11 21:59:28
Message-ID: 1084312767.3028.2160.camel@stromboli
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 2004-05-11 at 22:15, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > I need to send a signal from a backend to the archiver process.
>
> > 1. What signal should I use?
>
> SIGUSR1 or SIGUSR2 would be the safest choices.
>
> > 2. How do I give the processid of the archiver to the backend? The
> > archiver may restart at any time, so its pid could change after a
> > backend is forked.
>
> My answer would be "don't". Send a signal to the postmaster and
> let it signal the current archiver child. Use the existing
> SendPostmasterSignal() code for the first part of this.
>

Brilliant - very clean. Many thanks. Best Regards, Simon Riggs

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2004-05-11 22:02:01 Re: XLog: how to log?
Previous Message Simon Riggs 2004-05-11 21:58:25 Re: XLog: how to log?