BUG #7549: max_connections check should query master when starting standby

On Mon, Sep 17, 2012 at 11:46 PM, Craig Ringer <ringerc@ringerc.id.au>wrote:

> On 09/18/2012 07:57 AM, Fujii Masao wrote:
>
>> If you change the max_connections on the master, you need to take a
>> fresh backup from the master and start the standby from it.
>>
>
> WTF, really?
>
> What else breaks the replication and forces a re-clone?
>
> Another WTF from me too.

I can understand moving from read-only to read-write, but internally *why*
does this happen?  If it is the case, it needs to be clearly documented.

(mental note to test this and report back).

Why would this create a different timeline?

Best Wishes,
Chris Travers