Hello,
I am experimenting with the cascade standby and hit a problem which is reproducible with the current HEAD. I haven't tried other branches, but not sure if the test setup I am trying even works for older releases because of the timeline ID issue.
Anyways, I set up a cascaded standby such that it streams from the first standby and then stopped the original master and promoted the first standby to be the new master. If I then try to smart shutdown the cascaded standby, it fails after waiting for the walreceiver to terminate. What's worse, the walsender on the first standby gets into an infinite loop consuming 100% CPU.
I tried to investigate this a bit, but haven't made progress worth reporting. I can spend more time, but just wanted to make sure that I'm not trying something which is a known issue or limitation. BTW, this is on my Macbook Pro. Attached is the script that I used to set up the environment. You will need to modify it for your setup though.
Thanks,
