From: Jerry Sievers <gsievers19@comcast.net>
To: Alanoly Andrews <alanolya@invera.com>
Cc: "'pgsql-admin\@postgresql.org'" <pgsql-admin@postgresql.org>
Subject: Re: Warm Standby on 8.4.7
References: <09B23E7BF70425478C1330D893A722C603075D2AA7@MailSVR.invera.com>
Date: Thu, 14 Apr 2011 07:13:19 -0400
In-Reply-To: <09B23E7BF70425478C1330D893A722C603075D2AA7@MailSVR.invera.com>
	(Alanoly Andrews's message of "Wed, 13 Apr 2011 15:53:33 -0400")
Message-ID: <87ei55w0fk.fsf@comcast.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Alanoly Andrews <alanolya@invera.com> writes:

> Hello,
>
> Is it possible to set up a warm standby pair of postgres instances
> without using the pg_standby utility? The PG manuals appear to say it
> is possible. But I dont see the details of how to set this up. How
> do you keep the standby instance in permanent recovery mode?

Certainly if you implement the same or possibly extended logic yourself
in whatever language you are comfortable with.

Myself and others have been doing warm-standby since WALs were invented
:-)

When the company I work for started requiring that WS servers be helf
back a configurable time lag from production, I made some minor mods to
our version of the standby script, now written in Python, to make it
happen.

WALs now have to pass sanity and aging checks before being applied.

HTH


-- 
Jerry Sievers
Postgres DBA/Development Consulting
e: gsievers19@comcast.net
p: 305.321.1144