From: Tom Lane <tgl@sss.pgh.pa.us>
To: d.wall@computer.org
Cc: pgsql-admin@postgresql.org
Subject: Re: WAL recovery, stop and resume recovery?
Date: Fri, 11 Jan 2008 15:33:51 -0500
Message-ID: <24388.1200083631@sss.pgh.pa.us> (raw)
In-Reply-To: <4787C7A7.3000503@computer.org>
References: <4787C7A7.3000503@computer.org>
David Wall <d.wall@computer.org> writes:
> Is it allowable to have a backup database in recovery mode, then stop
> recovery (in this case, by putting the trigger file in place to stop
> pg_standby), check out that the backup db appears up to date, stop the
> now active backup db, and then restart it in recover mode again to have
> it resume its backup role?
No. Once you've done any transactions in the backup DB, its transaction
history has diverged from the master and you can't resume tracking the
master. It shouldn't even let you try --- what shenanigans did you pull
to force it back into recovery mode?
There's some work being done on allowing read-only queries against an
in-recovery database, which I think would satisfy your desire to see if
the backup were sane or not. But I wouldn't bet money on that getting
into the system anytime soon. It's definitely not something you can
cobble up from spare parts.
regards, tom lane
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, d.wall@computer.org
Subject: Re: WAL recovery, stop and resume recovery?
In-Reply-To: <24388.1200083631@sss.pgh.pa.us>
* 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