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

From hubert depesz lubaczewski
Subject Re: Problem with streaming replication, backups, and recovery (9.0.x)
Date
Msg-id 20110328151148.GA2436@depesz.com
Whole thread Raw
In response to Re: Problem with streaming replication, backups, and recovery (9.0.x)  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Problem with streaming replication, backups, and recovery (9.0.x)
Re: Problem with streaming replication, backups, and recovery (9.0.x)
List pgsql-hackers
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?

Best regards,

depesz

-- 
The best thing about modern society is how easy it is to avoid contact with it.
                  http://depesz.com/
 


pgsql-hackers by date:

Previous
From: Yeb Havinga
Date:
Subject: Re: Recursive containment of composite types
Next
From: Tom Lane
Date:
Subject: Re: Recursive containment of composite types