Re: Base Backups from PITR Standby

Brian Wipf <brian(at)clickspace(dot)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