Draft
Conversation
Adds max_connections configuration to limit concurrent client connections: - New MaxConnections field in Config struct - Connection limit check in handleConnection() with atomic counter - New duckgres_connection_limit_rejects_total metric - DUCKGRES_MAX_CONNECTIONS env var and YAML config support - Connections are rejected when limit is reached (default: 0 = unlimited) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
EDsCODE
force-pushed
the
feature/connection-limits
branch
from
2614ec5 to
e395fd7
Compare
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
Changes
MaxConnectionsto Config struct (default: 0 = unlimited)max_connectionsYAML config andDUCKGRES_MAX_CONNECTIONSenv varhandleConnection()using atomic counterduckgres_connection_limit_rejects_totalPrometheus metricConfiguration
Test plan
🤖 Generated with Claude Code