See postgis.go where a new error state is created if the connection URI does not include a user. A user isn't required in libpq connection URIs. This makes sense if using a Trust Authentication with unix domain sockets
Given #1044 and #1016 it would be much better, I think, to avoid parsing and attempting to validate the connection parameters (env vars and connection string) and just catch errors from pgx when connecting.
See postgis.go where a new error state is created if the connection URI does not include a user. A user isn't required in libpq connection URIs. This makes sense if using a Trust Authentication with unix domain sockets
Given #1044 and #1016 it would be much better, I think, to avoid parsing and attempting to validate the connection parameters (env vars and connection string) and just catch errors from pgx when connecting.