Connection Pooling
- Dominant language
- Rust
- Stars
- 30
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
# Configuration
- [x] YAML file
- [ ] Using extension (FFI)
- [x] Using PgGateway as a crate
---
# Pool mode
- [ ] Session
- [ ] Transaction
- [ ] Statement
- [ ] Auto
# Pool configuration/Proxy
- [ ] Max client connection
- [ ] Per instance
- [ ] Per pool
- [ ] Global per pool
- [ ] Max pool size
- [ ] Global per pool
- [ ] Per pool
- [ ] Min pool size
- [ ] Global per pool
- [ ] Per pool
- [ ] Max db connection - db level configuration
- [ ] Global
- [ ] DB Level
- [ ] Max client connections per db
- [ ] Max server connection per user
- [ ] Max prepared statements
- [ ] Server reset query
- [ ] Server lifetime
- [ ] Client lifetime
- [ ] Server idle timeout
- [ ] Server connect timeout
- [ ] Server login retry delay
- [ ] Track extra parameters
- [ ] Ignore startup parameters
- [ ] `SET` statement tracking
- [ ] Query timeout
- [ ] Query wait timeout
- [ ] Cancel query wait timeout
- [ ] Idle transaction timeout
- [ ] In Transaction timeout
# Health Check
- [ ] Server check query
- [ ] Health check interval
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the existing YAML configuration and PgGateway crate integration referenced in the issue. Narrow the checklist to one specific pool mode or configuration item before choosing an implementation path. Done should mean that the selected item is implemented and its configuration and behavior are verifiable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, rust
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100