| 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 12:19:33 |
| Message-ID: | 20110328121933.GA17060@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
Is it intentional and/or does it serve some greater good? I mean -
ability to make backups on slave without ever bothering master was
pretty interesting.
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 | Simon Riggs | 2011-03-28 12:34:57 | Re: Additional options for Sync Replication |
| Previous Message | Robert Haas | 2011-03-28 12:18:03 | Re: Problem with streaming replication, backups, and recovery (9.0.x) |