Fix pgpool_setup so that it fail back to full restore if failed in restarting.
authorTatsuo Ishii <ishii@sraoss.co.jp>
Wed, 31 Mar 2021 07:09:13 +0000 (16:09 +0900)
committerTatsuo Ishii <ishii@sraoss.co.jp>
Wed, 31 Mar 2021 07:09:13 +0000 (16:09 +0900)
commit4462f9f1367ec3d22274af28777b084fb9f198ea
tree633f2737fd325b514e0aae5f91e365d82f374bb7
parent26cd47f12aebd1d7b4f623d7b1f12ebc90390059
Fix pgpool_setup so that it fail back to full restore if failed in restarting.

While taking care of "[pgpool-general: 7456] Expected behaviour after pcp_detach_node ?"

https://www.pgpool.net/pipermail/pgpool-general/2021-March/007514.html

I noticed that restarting target server in follow primary script could
fail.  This could happen when former primary goes to down status using
pcp_detach_node.  The former primary will not start due to timeline
and LSN divergence.  To fix this, fail back to full restore using
pg_recovery if restarting server.
src/test/pgpool_setup.in