Geo: for zero-downtime upgrades, ask to refresh FDW after post-deployment migrations
From the discussion in #33252 (comment 225554683):
On our documentation, we mention that users need to verify the Geo configuration and dependencies on each secondary node after running the post-deployment migrations on the primary. Should we update it to include a new step to refresh the foreign tables or make the Rake task
gitlab:geo:checksmart enough to handle this?
Edited by Toon Claes