Describe the bug
CONFIGURATION.md claims the connection-pool defaults are:
| Name |
Default |
| DB_MIN_POOL_SIZE |
16 |
| DB_MAX_POOL_SIZE |
32 |
But src/database/client.ts actually defaults to min: 0 and max: 3:
pool: {
min: process.env.DB_MIN_POOL_SIZE ? Number(process.env.DB_MIN_POOL_SIZE) : 0,
max: process.env.DB_MAX_POOL_SIZE ? Number(process.env.DB_MAX_POOL_SIZE) : 3,
...
}
The same mismatch applies to every RRn_DB_MIN_POOL_SIZE / RRn_DB_MAX_POOL_SIZE row (documented as 16/32, code default 0/3).
This matters because the worker error handler in src/app/worker.ts explicitly tells operators to "increase DB_MAX_POOL_SIZE" when connection acquisition fails but the doc leads them to believe the pool is already large (32) when it is really 3.
Expected behavior
The documented defaults should match the code (min 0, max 3), or a note should clarify that docker-compose.yml overrides them.
System: Linux, Docker, v2.1.0
Describe the bug
CONFIGURATION.mdclaims the connection-pool defaults are:But
src/database/client.tsactually defaults tomin: 0andmax: 3:The same mismatch applies to every
RRn_DB_MIN_POOL_SIZE/RRn_DB_MAX_POOL_SIZErow (documented as 16/32, code default 0/3).This matters because the worker error handler in
src/app/worker.tsexplicitly tells operators to "increase DB_MAX_POOL_SIZE" when connection acquisition fails but the doc leads them to believe the pool is already large (32) when it is really 3.Expected behavior
The documented defaults should match the code (min
0, max3), or a note should clarify thatdocker-compose.ymloverrides them.System: Linux, Docker, v2.1.0