From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Problem with streaming replication, backups, and recovery (9.0.x) |
Date: | 2011-03-28 15:11:48 |
Message-ID: | 20110328151148.GA2436@depesz.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-03-28 15:14:23 | Re: Recursive containment of composite types |
Previous Message | Yeb Havinga | 2011-03-28 15:04:52 | Re: Recursive containment of composite types |