Re: PITR Signalling the Archiver

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
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:15:51
Message-ID: 15249.1084310151@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2004-05-11 21:26:00 Re: XLog: how to log?
Previous Message Michael Brusser 2004-05-11 21:09:17 database errors