Regarding the following questions:
A few more questions in this thread:
1. With the wait-for-next-file script scenario, what happens with
recovery.conf? Does it ever become recovery.done? What happens in the
event of needing to recover? Does the script need a trigger to say,
Okay,
On Tue, 2006-03-14 at 16:41 -0600, Thomas F. O'Connell wrote:
On Mar 4, 2006, at 3:56 AM, Simon Riggs wrote:
On Fri, 2006-03-03 at 12:03 -0600, Thomas F. O'Connell wrote:
On Mar 3, 2006, at 11:54 AM, Simon Riggs wrote:
On Thu, 2006-03-02 at 16:38 -0600, Thomas F. O'Connell wrote:
On Mar 4, 2006, at 3:56 AM, Simon Riggs wrote:
On Fri, 2006-03-03 at 12:03 -0600, Thomas F. O'Connell wrote:
On Mar 3, 2006, at 11:54 AM, Simon Riggs wrote:
On Thu, 2006-03-02 at 16:38 -0600, Thomas F. O'Connell wrote:
Ideally, I'd be able to take a base backup of a production system,
copy
On Fri, 2006-03-03 at 12:03 -0600, Thomas F. O'Connell wrote:
On Mar 3, 2006, at 11:54 AM, Simon Riggs wrote:
On Thu, 2006-03-02 at 16:38 -0600, Thomas F. O'Connell wrote:
Ideally, I'd be able to take a base backup of a production system,
copy it to a remote system, which is also the
will not
be propagated back to your master.
Regards
Andy
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Thomas F. O'Connell
Sent: Thursday, 02 March, 2006 10:39 PM
To: PGSQL Admin
Subject: [ADMIN] PITR as Online Backup Solution
I'm administering a database
On Thu, 2006-03-02 at 16:38 -0600, Thomas F. O'Connell wrote:
I'm administering a database that is not immediately a good candidate
for replication via Slony. As an interim solution, I'd like to give
PITR a shot. The primary goal is to have a failover scenario that
allows for recovery
On Fri, 2006-03-03 at 10:23 +, Andy Shellam wrote:
Then you would have to find a method of telling the script
that you wish to bring the database up and it will exit and allow PGSQL to
come up at the current state with the latest data.
Replication sounds like a better option
If you want
On Mar 3, 2006, at 11:54 AM, Simon Riggs wrote:
On Thu, 2006-03-02 at 16:38 -0600, Thomas F. O'Connell wrote:
Ideally, I'd be able to take a base backup of a production system,
copy it to a remote system, which is also the repository for segment
files generated by archive_command, and
On Mar 3, 2006, at 12:00 PM, Simon Riggs wrote:
On Fri, 2006-03-03 at 10:23 +, Andy Shellam wrote:
Then you would have to find a method of telling the script
that you wish to bring the database up and it will exit and allow
PGSQL to
come up at the current state with the latest data.
On Fri, Mar 03, 2006 at 10:23:57AM -, Andy Shellam wrote:
Hi Thomas,
I've been trying to get a similar system up and running, and I have to say
one point in the documentation isn't particularly clear.
It says that you can string together an almost endless supply of WAL logs to
replay
I'm administering a database that is not immediately a good candidate
for replication via Slony. As an interim solution, I'd like to give
PITR a shot. The primary goal is to have a failover scenario that
allows for recovery within a window that's much smaller than it would
be if the only
11 matches
Mail list logo
