Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: handle max wal senders error #1300

Merged
merged 4 commits into from
Feb 18, 2025
Merged

Conversation

filipecabaco
Copy link
Member

What kind of change does this PR introduce?

Handles number of requested standby connections exceeds max_wal_senders on replication startup

Copy link

vercel bot commented Feb 14, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
realtime-demo ⬜️ Ignored (Inspect) Visit Preview Feb 18, 2025 3:32pm

@filipecabaco filipecabaco force-pushed the fix/handle-max-wal-senders branch from 0e6f212 to bb36d97 Compare February 18, 2025 15:31
@filipecabaco filipecabaco force-pushed the fix/handle-max-wal-senders branch from bb36d97 to 5a94a6d Compare February 18, 2025 15:32
@coveralls
Copy link

coveralls commented Feb 18, 2025

Coverage Status

coverage: 81.858% (+0.6%) from 81.244%
when pulling 5a94a6d on fix/handle-max-wal-senders
into 2686dad on main.

@filipecabaco filipecabaco merged commit eebd6f7 into main Feb 18, 2025
6 checks passed
@filipecabaco filipecabaco deleted the fix/handle-max-wal-senders branch February 18, 2025 18:13
@kiwicopple
Copy link
Member

🎉 This PR is included in version 2.34.24 🎉

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
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants