fix: region rebalancing for Postgres Changes #1464
Merged
+80
−14
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
filipecabaco
approved these changes
Jul 16, 2025
edgurgel
force-pushed
the
fix/subscription-manager-rebalance
branch
from
90f7c3f to
7752e54
Compare
|
🎉 This PR is included in version 2.41.5 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Follow-up from #1455 to also rebalance our Postgres Changes pool of processes to the correct region
What is the current behavior?
If the Postgres Changes pool of processes start in the wrong region they might have a much higher latency that can impact performance.
What is the new behavior?
Every X time it will check if it's running at the correct region. If it's not then it stops. The next time it runs it will start at the right place.
Additional context
Add any other context or screenshots.