Hot standby, pausing recovery - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Hot standby, pausing recovery
Date
Msg-id 4AD813AE.60508@enterprisedb.com
Whole thread Raw
Responses Re: Hot standby, pausing recovery
List pgsql-hackers
This if-block is misplaced:

>             case RECOVERY_TARGET_STOP_IMMEDIATE:
>             case RECOVERY_TARGET_STOP_XID:
>             case RECOVERY_TARGET_STOP_TIME:
>                     paused = false;
>                     break;
> 
>             /*
>              * If we're paused, and mode has changed reset to allow new settings
>              * to apply and maybe allow us to continue.
>              */
>             if (paused && prevRecoveryTargetMode != recoveryTargetMode)
>                 paused = false;
> 
>             case RECOVERY_TARGET_PAUSE_XID:

Where was that supposed to go?

In advance-mode, we will merrilly skip over a WAL record that's a
recovery stop target. Is that a bug or a feature?

If you pause recovery, and then continue, we reset to "target none"
mode, even if a stopping point was set previously. That doesn't seem
right to me.

--  Heikki Linnakangas EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Hot standby, recovery_starts_paused
Next
From: Simon Riggs
Date:
Subject: Re: Hot standby, pausing recovery