Re: PITR potentially broken in 9.2 - Mailing list pgsql-bugs

From Heikki Linnakangas
Subject Re: PITR potentially broken in 9.2
Date
Msg-id 50B613A2.3080601@vmware.com
Whole thread Raw
In response to Re: PITR potentially broken in 9.2  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: PITR potentially broken in 9.2  (Andres Freund <andres@2ndquadrant.com>)
Re: PITR potentially broken in 9.2  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-bugs
On 28.11.2012 15:26, Andres Freund wrote:
> Hm. Are you sure its actually reading your backup file? Its hard to say
> without DEBUG1 output but I would tentatively say its not reading it at
> all because the the "redo starts at ..." message indicates its not using
> the checkpoint location from the backup file.

By backup file, you mean the backup history file? Since 9.0, recovery
does not read the backup history file, it's for informational/debugging
purposes only. All the information recovery needs is in the
backup_label, and an end-of-backup WAL record marks the location where
pg_stop_backup() was called, ie. how far the WAL must be replayed for
the backup to be consistent.

> Can you reproduce the issue? If so, can you give an exact guide? If not,
> do you still have the datadir et al. from above?

I just committed a fix for this, but if you can, it would still be nice
if you could double-check that it now really works.

- Heikki

pgsql-bugs by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: PITR potentially broken in 9.2
Next
From: Andres Freund
Date:
Subject: Re: PITR potentially broken in 9.2