On Tue, Mar 29, 2011 at 11:20:48AM +0900, Fujii Masao wrote:
> On Tue, Mar 29, 2011 at 12:11 AM, hubert depesz lubaczewski
> <[email protected]> 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.
no, i don't use.
hmm .. i am nearly 100% certain that previous pgs did in fact check if the end
of recovery is reached.
Best regards,
depesz
--
The best thing about modern society is how easy it is to avoid contact with it.
http://depesz.com/
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
