We have decided to use Postgres and digital oceans managed databases for our next project. This database will handle about 10 million page visits a month, with certain points having spikes in traffic. We created a database, and were able to connect to it just fine.

We created a new connection pool, and the connection details are different than our other database. It has a different port and a different database listed. When we try to connect with the connection pool details, we get the error database "test-pool" does not exist

We are also using sequelize 5.xx and node js. Haven’t had any issues up until trying to utilize connection pooling. Any ideas or suggestions?

1 comment
  • Having the same issue here - I have a database created and am constantly running into the error FATAL: remaining connection slots are reserved for non-replication superuser connections.

    Decided to create a connection pool and use that to connect to the database instead.

    The connection parameters show a different port, but I am unable to connect to that port, with the error database does not exist.

    Any help would be much appreciated!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
1 answer

To answer my own question, use the pool name to connect instead of the db name.

postgresql://{user_name}:{password}@datalab-do-user-6674409-0.b.db.ondigitalocean.com:{pool_port_number}/{pool_name}?sslmode=require

I hope this helps people who might have the same question out.

Submit an Answer