From: CG <cgg007@yahoo.com>
To: pgsql-admin@postgresql.org, Jeff Frost <jeff@frostconsultingllc.com>
To: Andy Shellam <andy.shellam@mailnetwork.co.uk>
Subject: Re: WAL recovery
Date: Wed, 22 Feb 2006 11:55:45 -0800 (PST)
Message-ID: <20060222195545.39914.qmail@web32512.mail.mud.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0602220921260.11795@glacier.frostconsultingllc.com>
Andy,
FWIW, I /think/ the replication scheme you are trying to carry out is
implemented in Command Prompt's "Mammoth PostgreSQL Replicator" product. From
what I understand, their system will independently copy over and replay
"TransactionLog" files (translate: WAL files?) on your slave databases in a
continuous stream or in a batch. They describe a few other features in their
product that might make the commercial option worthwhile to try.
CG
--- Jeff Frost <jeff@frostconsultingllc.com> wrote:
> On Wed, 22 Feb 2006, Andy Shellam wrote:
>
> > However, if I delete my PG data directory, restore the same base backup
> from
> > yesterday, and begin recovery, it recovers right up until the last log
> file,
> > which the previous roll-forward attempt fails.
> > The log files were fully archived off the live server to begin with so I
> > can't see it's that they've changed or anything.
> >
> > Is this scenario possible - that you can keep rolling forward over log
> files
> > as long as necessary, or do you always have to start from a base backup?
> > Nothing is changing on the spare, it's literally a sitting duck.
>
> You must always start with a base backup when you begin the restore otherwise
>
> the system does not know where to begin the recovery. What I have done in
> the
> past on a similar system is keep the secondary DB shutdown and make base
> backups as often as possible so the recovery time is suitably short when the
> secondary is needed. Also a good idea to do test recovers on occassion to
> make sure you don't have any corrupt WAL files. If you use rsync, then you
> can make the base backup pretty quickly depending on how much of your DB
> changes.
>
> --
> Jeff Frost, Owner <jeff@frostconsultingllc.com>
> Frost Consulting, LLC http://www.frostconsultingllc.com/
> Phone: 650-780-7908 FAX: 650-649-1954
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: cgg007@yahoo.com, jeff@frostconsultingllc.com, andy.shellam@mailnetwork.co.uk
Subject: Re: WAL recovery
In-Reply-To: <20060222195545.39914.qmail@web32512.mail.mud.yahoo.com>
References: <Pine.LNX.4.64.0602220921260.11795@glacier.frostconsultingllc.com> <20060222195545.39914.qmail@web32512.mail.mud.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox