Jack Christensen

FWIW, multi errors are implemented in 8db971660e43a944c777d5e4fcfcb7885acb7566. This will produce errors like: ``` failed to connect to `user=postgres database=pgx_test`: lookup foo.invalid: no such host [::1]:1 (localhost): dial error: dial tcp...

If ipv4 worked then no error would be returned. The error list is only returned if no attempt succeeds.

This is matching the behavior of libpq. See https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-MULTIPLE-HOSTS. > In either format, a single host name can translate to multiple network addresses. A common example of this is a...

@laskoviymishka Personally, I don't plan on porting back to v4. I'm not sure how far that part of the code has diverged between v4 and v5 and I'm typically only...

I don't think this will work in the general case as is. The binary format of `jsonb` includes a 1 byte prefix that must be stripped. Beyond that, some care...

I suspect there are unresolvable ambiguities regarding `string` `bytea`. Writing the string to a PostgreSQL bytea at least appears to work because pgx sends any `string` to PostgreSQL in the...

> For string itself, it seems like I would have to unregister ByteaCodec and register a custom one? Am I mistaken? Or is there an easier way? Maybe just using...

I don't know. As you say it shouldn't panic. The only think that jumps out at me is the use of pgx v4. v5 has been out for over a...

@Se7ge There is no guide as such, but the changelog for the initial release of v5 includes a list of significant changes: https://github.com/jackc/pgx/blob/master/CHANGELOG.md#v500-september-17-2022

> As the behaviour differs from database/sql and is likely to cause confusion I believe it's probably a bug (I guess it could be an attempt to reduce allocations). It...