On Tue, Dec 18, 2012 at 2:39 AM, Heikki Linnakangas
wrote:
> (This is different from the other issue related to timeline switches I just
> posted about. There's no timeline switch involved in this one.)
>
> If you do "pg_basebackup -x" against a standby server, in some circumstances
> the backup f
On 18.12.2012 11:30, Simon Riggs wrote:
On 18 December 2012 09:18, Heikki Linnakangas wrote:
That seems correct to me. The backup is considered valid after reaching
0/1764F48, which is where the checkpoint record ends. minRecoveryPoint is
set to the same. What do you think it should be set to?
On 18 December 2012 09:18, Heikki Linnakangas wrote:
> That seems correct to me. The backup is considered valid after reaching
> 0/1764F48, which is where the checkpoint record ends. minRecoveryPoint is
> set to the same. What do you think it should be set to?
I already said?
--
Simon Riggs
On 18.12.2012 00:35, Simon Riggs wrote:
On 17 December 2012 17:39, Heikki Linnakangas wrote:
(This is different from the other issue related to timeline switches I just
posted about. There's no timeline switch involved in this one.)
If you do "pg_basebackup -x" against a standby server, in som
On 17 December 2012 17:39, Heikki Linnakangas wrote:
> (This is different from the other issue related to timeline switches I just
> posted about. There's no timeline switch involved in this one.)
>
> If you do "pg_basebackup -x" against a standby server, in some circumstances
> the backup fails t
(This is different from the other issue related to timeline switches I
just posted about. There's no timeline switch involved in this one.)
If you do "pg_basebackup -x" against a standby server, in some
circumstances the backup fails to restore with error like this:
C 2012-12-17 19:09:44.042
