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.
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
pgsql-hackers by date
|Next:||From: Heikki Linnakangas||Date: 2010-01-18 06:28:13|
|Subject: Re: Hot Standby and handling max_standby_delay|
|Previous:||From: Fujii Masao||Date: 2010-01-18 05:08:23|
|Subject: Re: New XLOG record indicating WAL-skipping|