Re: Problem with streaming replication, backups, and recovery (9.0.x) - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Problem with streaming replication, backups, and recovery (9.0.x)
Date
Msg-id AANLkTikNQd8jXYuarhcoYe_2sRBPSf0_3N_o7OrkuLj-@mail.gmail.com
Whole thread Raw
In response to Re: Problem with streaming replication, backups, and recovery (9.0.x)  (hubert depesz lubaczewski <depesz@depesz.com>)
Responses Re: Problem with streaming replication, backups, and recovery (9.0.x)
List pgsql-hackers
On Tue, Mar 29, 2011 at 12:11 AM, hubert depesz lubaczewski
<depesz@depesz.com> wrote:
> On Mon, Mar 28, 2011 at 01:48:13PM +0900, Fujii Masao wrote:
>> In 9.0, recovery doesn't read a backup history file. That FATAL error happens
>> if recovery ends before it reads the WAL record which was generated by
>> pg_stop_backup(). IOW, recovery gets the recovery ending location from WAL
>> record not backup history file. Since you didn't run pg_stop_backup() and there
>> is no WAL record containing the recovery ending location, you got that error.
>>
>> If you want to take hot backup from the standby, you need to do the procedure
>> explained in
>> http://wiki.postgresql.org/wiki/Incrementally_Updated_Backups
>
> one more question. how come that I can use this backup to make
> standalone pg, and it starts without any problem, but when I start it as
> sr slave, let it run for some time, and then promote to standalone, it
> breaks?

Did you use recovery.conf to start standalone PostgreSQL? If not,
recovery doesn't check whether it reaches the recovery ending position
or not. So I guess no problem didn't happen.

Regards,

-- 
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center


pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Problem with streaming replication, backups, and recovery (9.0.x)
Next
From: Joseph Adams
Date:
Subject: Re: Another swing at JSON