pgxmock VS scany

It's not the right call IMO to skip mocking the database connection to achieve 100% test coverage. How your app will behave in failure scenarios that are impossible to imitate during integration tests is part of the software contract. If your choice is to panic, or return an error, document that by testing that behavior. If another dev, or future you inadvertently breaks the contract, the test suite will fail. That's what you want. For unit tests against your database you should be using either go-sqlmock if testing against database/sql or pgxmock if testing against pgx. That being said, the points raised elsewhere in this thread regarding unit tests potentially hiding edge cases in terms of how an actual database will interact with your application that are not reflective of your understanding when writing mocks are 100% valid. You should do both. Unit test your app and write integration tests as well. On my team, we run integration tests using docker-compose.

For postgres only but pgxmock is similarly excellent

When I don't use one, I'm typically using SQLx or (if using Postgres) pgx with scany https://github.com/georgysavva/scany (slightly better API than SQLx and great performance since you can use the native interface from pgx if desired whereas many database drivers only offer the text-based interface).

If you want something like sqlx and you already know you're using pgx, a better choice is probably https://github.com/georgysavva/scany since you can use the native interface and get the same key features.

github.com/georgysavva/scany (v1.1.0)

I like to use pgxscan from https://github.com/georgysavva/scany

There's also bqb. We use it in production at our company -- much better than raw SQL. If you couple it with something like scany then you get more of the ORM benefits without the complexity.