2011/8/5 Jun Ishiduka <ishizuka.jun@po.ntts.co.jp>:
>> I will provide a patch which can exeute pg_start/stop_backup
>> including to solve above comment and conditions in next stage.
>> Then please review.
>
> done.
great !
>
>
> * Procedure
>
> 1. Call pg_start_backup('x') on the standby.
> 2. Take a backup of the data dir.
> 3. Call pg_stop_backup() on the standby.
> 4. Copy the control file on the standby to the backup.
> 5. Check whether the control file is status during hot standby with pg_controldata.
> -> If the standby promote between 3. and 4., the backup can not recovery.
> -> pg_control is that "Minimum recovery ending location" is equals 0/0.
> -> backup-end record is not written.
>
> * Not correspond yet
>
> * full_page_write = off
> -> If the primary is "full_page_write = off", archive recovery may not act
> normally. Therefore the standby may need to check whether "full_page_write
> = off" to WAL.
Isn't having a standby make the full_page_write = on in all case
(bypass configuration) ?
>
> --------------------------------------------
> Jun Ishizuka
> NTT Software Corporation
> TEL：045-317-7018
> E-Mail: ishizuka.jun@po.ntts.co.jp
> --------------------------------------------
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
>
--
Cédric Villemain +33 (0)6 20 30 22 52
http://2ndQuadrant.fr/
PostgreSQL: Support 24x7 - Développement, Expertise et Formation