Re: Base Backups from PITR Standby - Mailing list pgsql-general

From Tom Lane
Subject Re: Base Backups from PITR Standby
Date
Msg-id 16140.1193720810@sss.pgh.pa.us
Whole thread Raw
In response to Base Backups from PITR Standby  (Brian Wipf <brian@clickspace.com>)
Responses Re: Base Backups from PITR Standby  (Brian Wipf <brian@clickspace.com>)
List pgsql-general
Brian Wipf <brian@clickspace.com> writes:
> The process I use that leads to the warnings is simple:

> I use pg_controldata to determine the current checkpoint WAL location
> of the standby server. I ensure I have this WAL file and all newer
> WALs. I backup all files under the standby's database cluster
> directory, including all tablespaces, which are soft linked. I restore
> the database cluster directory to its new location and create soft
> links in pg_tblspc to point to the proper tablespace directories just
> backed up. I create the pg_xlog directory containing an archive_status
> directory.

This seems not exactly per spec.  Why are you not using pg_start_backup
and pg_stop_backup around the copying of the database files?

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Collation sequence and use of operatings system's locale
Next
From: Tom Lane
Date:
Subject: Re: SSL Connectivity on Solaris 10 x86