No connection pool with 'primary' found error when booting up

Hey, since I migrated my dev env to portgres, I often see this message. Anyone have insights why this is happening?

I think dynflow is fighting with rails for the connection pool. Try higher pool: value in database.yml

I’ve seen this with lots of widgets on the dashboard causing the connection pool to run out if you browse to another page before all widgets have loaded. increasing the pool size helps.

Weird, I already have 20. Will try, thanks.

That ought to be enough for anybody. Bill Gates.

2 Likes

I’ve increased this to 50 and I am still getting these. Something is not right.