From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | depesz(at)depesz(dot)com |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Problem with streaming replication, backups, and recovery (9.0.x) |
Date: | 2011-03-29 02:20:48 |
Message-ID: | AANLkTikNQd8jXYuarhcoYe_2sRBPSf0_3N_o7OrkuLj-@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Mar 29, 2011 at 12:11 AM, hubert depesz lubaczewski
<depesz(at)depesz(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Joseph Adams | 2011-03-29 02:24:10 | Re: Another swing at JSON |
Previous Message | Fujii Masao | 2011-03-29 02:13:07 | Re: Problem with streaming replication, backups, and recovery (9.0.x) |