Limit HikariCP pool size for shared DB cluster#184
Merged
Conversation
The shared DigitalOcean PostgreSQL cluster has limited connection slots. Reduces HikariCP pool from default 10 to max 5 / min idle 2 to leave room for other services on the cluster. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
remaining connection slots are reserved for roles with the SUPERUSER attributeerrors on the shared DO PostgreSQL clusterHIKARI_MAX_POOL_SIZEandHIKARI_MIN_IDLEenv varsContext
The shared DigitalOcean managed PostgreSQL cluster has ~22 connection slots. With mlb-stats (10), gif-clipper (10), and cartergrove-me (10) all using defaults, the cluster runs out of connections. This change is coordinated across all three repos.
Test plan
🤖 Generated with Claude Code