Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Re: Streaming replication, and walsender during recovery
On Mon, Jan 18, 2010 at 2:19 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> When I configured a cascaded standby (i.e, made the additional
> standby server connect to the standby), I got the following
> errors, and a cascaded standby didn't start replication.
>
> ERROR: timeline 0 of the primary does not match recovery target timeline 1
>
> I didn't care about that case so far. To avoid a confusing error
> message, we should forbid a startup of walsender during recovery,
> and emit a suitable message? Or support such cascade-configuration?
> Though I don't think that the latter is difficult to be implemented,
> ISTM it's not the time to do that now.
We got the consensus that the cascading standby feature should be
postponed to v9.1 or later. But when we wrongly make the standby
connect to another standby, the following confusing message is still
output.
FATAL: timeline 0 of the primary does not match recovery target timeline 1
How about emitting the following message instead? Here is the patch.
FATAL: recovery is in progress
HINT: cannot accept the standby server during recovery.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
Attachment: forbid_cascading_standby_0218.patch
Description: text/x-patch (567 bytes)
Description: text/x-patch (567 bytes)
In response to
- Streaming replication, and walsender during recovery at 2010-01-18 05:19:59 from Fujii Masao
Responses
- Re: Streaming replication, and walsender during recovery at 2010-03-16 09:11:56 from Heikki Linnakangas
pgsql-hackers by date
Next: From: Tom Lane Date: 2010-02-18 06:57:36 Subject: Re: alpha4 timing Previous: From: Fujii Masao Date: 2010-02-18 05:17:06 Subject: Streaming replication and unfit messages