4 ms·

yeah so I'm seeing a ton of "(Postgrex.Error) FATAL 53300 (too_many_connections) remaining connection slots are reserved for non-replication superuser connectio

yeah so I'm seeing a ton of "(Postgrex.Error) FATAL 53300 (too_many_connections) remaining connection slots are reserved for non-replication superuser connections", which I'm guessing means the pool size is too small? Although I've tried upping that, CPU, and memory, and none have seemed to fix it. My devops skills still aren't great so if anyone has any ideas on how to help, let me know! This might be a good opportunity to change the server to try out fly.io

VVVExobyte 5y ago
dbetteridge 5y ago
Pgbouncer is your friend for postgres dB's with lots of client connections. Larger pool size only helps if they're freed up quicker than they are used.
- LecroJS 5y ago
  Would you mind elaborating on the second point? Is this unique to larger pools? My inclination is that this would be true for pools of all sizes
  - psd1 5y ago
    I suspect GP meant: increasing pool size is only prolonging the inevitable I've also observed on other DBs that you can increase the connection pool but it shifts the problem to other resources.
    - LecroJS 5y ago
      Thanks for the clarification. Makes sense