On 24.10.2011 15:29, Fujii Masao wrote:
+ <listitem> + <para> + Copy the pg_control file from the cluster directory to the global + sub-directory of the backup. For example: + <programlisting> + cp $PGDATA/global/pg_control /mnt/server/backupdir/global + </programlisting> + </para> + </listitem>
Why is this step required? The control file is overwritten by information from the backup_label anyway, no?
+ <listitem> + <para> + Again connect to the database as a superuser, and execute + <function>pg_stop_backup</>. This terminates the backup mode, but does not + perform a switch to the next WAL segment, create a backup history file and + wait for all required WAL segments to be archived, + unlike that during normal processing. + </para> + </listitem>
How do you ensure that all the required WAL segments have been archived, then?
+ </orderedlist> + </para> + + <para> + You cannot use the <application>pg_basebackup</> tool to take the backup + from the standby. + </para>
Why not? We have cascading replication now. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
