On 29-Oct-07, at 11:06 PM, Tom Lane wrote:
Brian Wipf <brian@xxxxxxxxxxxxxx> 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?
I'm trying to take a base backup from the standby server in archive
recovery mode. I don't believe it's possible to connect to it to issue
pg_start_backup/pg_stop_backup.
http://www.postgresql.org/docs/current/interactive/warm-standby.html#BACKUP-INCREMENTAL-UPDATED
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org/
