From: Scott Whitney <swhitney@journyx.com>
To: pgsql-admin@postgresql.org
Subject: Another PITR question
Date: Wed, 22 Oct 2008 15:06:50 -0500
Message-ID: <20081022200650.4F5717E424E@mail.int.journyx.com> (raw)
Sorry for the repetition on some of this stuff. I'm just now learning it.
So, I've got my WALs archiving just fine, and I've got my base backup.
What I'd like to do is keep the standby server in recovery mode.
Docs say:
"If we continuously feed the series of WAL files to another machine that has
been loaded with the same base backup file, we have a "hot standby" system:
at any point we can bring up the second machine and it will have a
nearly-current copy of the database."
Yep. That's what I want, alright.
So, what I have is this:
Production server:
archive command: (pseudo code): stick 'em out in the mounted dir
Recovery server:
restore command: This is where it gets dicey, to me.
If I say:
restore_command = 'cp /mnt/server/archivedir/%f %p'
it will copy all existing WAL files from the archive dir into the xlog dir,
and when I start the postmaster it will replay them. However, I want the
standby to CONSTANTLY stay in recovery mode, not just restore the WALs it
finds when I start it.
Is this possible? Can someone explain or point me to some example docs
somewhere?
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: swhitney@journyx.com
Subject: Re: Another PITR question
In-Reply-To: <20081022200650.4F5717E424E@mail.int.journyx.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