Re: Warm-Backup configuration question

On 8/24/07, Kenji Morishige <kenjim(at)juniper(dot)net> wrote:
>
> I've got 2 identical servers configured exactly the same way, except for
> some
> minor differences for the WAL logging directories. I have both machines
> set up
> as a NFS server and client, so that the WAL archive gets written out to
> the
> local filesystem of the backup machine depending on which role the machine
> is
> currently configured for.
>
> I've been able to get the backup server syncronized by using the
> recover.conf
> file as described in the documenation, but I can't seem to write a generic
> shell
> script that will keep the warm-backup in a continously syncronizing
> mode. It
> always stops and renames the recover.conf to recover.done.
>
> I've tried to write an alternate restore command as follows:
>
> #!/usr/local/bin/bash
> if [ -e /export/raid/pgsql/recovery.stop ]; then
> exit 1
> fi
> if [ -e $1 ]; then
> `/bin/cp $1 $2`
> fi
> sleep 5
> exit 0
>
> The documenation says that it should return 0 only if it is
> successfull. My
> understanding is that the recovery script should continuously try to copy
> the
> archived data to the WAL directory so that the WARM-BACKUP server can
> syncronize. I'd like to have the WARM-BACKUP always be only a few minutes
> behind in syncronization from the PRIMARY without human intervention. I
> can
> write a cronjob to clean out the WAL archive directory accordingly.
>
> I would be extremely gratefull for any assistance from anyone with a
> similar
> configuration. I must be confused by how the restore_command is supposed
> to
> work.
>
>
>
Why don't you just use pg_standby from contrib.

Regards

MP