Error: P1002 database server was reached but timed out

Bug description

I was running prisma migrate dev and ran into this error.

Error: P1002

The database server at `xx.xx.xx.xx`:`5432` was reached but timed out.

Please try again.

Please make sure your database server is running at `xx.xx.xx.xx`:`5432`.

I’m not using pgBouncer. This is my connection string: postgres://<XXXXXXXXXX>/defaultdb?connection_limit=3&connection_timeout=30&pool_timeout=30

I looked at #6053

How to reproduce

This is a random error.

Expected behavior

Primsa migrate happens as expected

Prisma information

Environment & setup

• OS: Mac OS 10.15.7
• Database: Postgres
• Node.js version: 15.14.0
• Prisma version:

prisma               : 2.21.2
@prisma/client       : 2.21.2
Current platform     : darwin
Query Engine         : query-engine e421996c87d5f3c8f7eeadd502d4ad402c89464d (at node_modules/@prisma/engines/query-engine-darwin)
Migration Engine     : migration-engine-cli e421996c87d5f3c8f7eeadd502d4ad402c89464d (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine : introspection-core e421996c87d5f3c8f7eeadd502d4ad402c89464d (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary        : prisma-fmt e421996c87d5f3c8f7eeadd502d4ad402c89464d (at node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash : e421996c87d5f3c8f7eeadd502d4ad402c89464d
Studio               : 0.371.0

[ChukaEbi]

@janpio I am running npx prisma migrate dev and I expected it to just add a uniqueness constraint to an existing field in a table.

[janpio]

@gregorcee123 @matt-development-work Are you also using migrate dev when you get this? If not, please open a new issue and provide all the information you have so we can understand better. Thanks.