You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I have two PostgreSql clusters running on two different sites(active and standby). For some reason, my standby cluster ran into a problem with all its postgres pods in "start failed" state. The log from the standby cluster pods shows the below.
"latest checkpoint is at X on timeline Y, but in the history of request timeline, the server forked off from that timeline at Z"
Please suggest any steps to bring my standby cluster back online again. Thanks!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I have two PostgreSql clusters running on two different sites(active and standby). For some reason, my standby cluster ran into a problem with all its postgres pods in "start failed" state. The log from the standby cluster pods shows the below.
"latest checkpoint is at X on timeline Y, but in the history of request timeline, the server forked off from that timeline at Z"
Please suggest any steps to bring my standby cluster back online again. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions