| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Jun Ishiduka <ishizuka(dot)jun(at)po(dot)ntts(dot)co(dot)jp>, ssinger_pg(at)sympatico(dot)ca, simon(at)2ndquadrant(dot)com, pgsql-hackers(at)postgresql(dot)org, magnus(at)hagander(dot)net, robertmhaas(at)gmail(dot)com, cedric(dot)villemain(dot)debian(at)gmail(dot)com |
| Subject: | Re: Online base backup from the hot-standby |
| Date: | 2011-10-24 15:24:28 |
| Message-ID: | 4EA5832C.9070607@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-10-24 15:28:35 | Re: autovacuum and orphaned large objects |
| Previous Message | Robert Haas | 2011-10-24 15:10:22 | Re: termination of backend waiting for sync rep generates a junk log message |