Jack Christensen

Candidate solution: https://github.com/jackc/pgx/pull/2020

Perhaps we should have a better error message, but I don't think that your example *should* work. The `*StructByName*` helpers are supposed to work independently of column order. There is...

> From looking at the lookupHost code in lookup_unix.go, it looks like the issue is that pgx tries to resolve the hostname of the server well before it tries to...

Also, it appears that the change as a whole would make all error messages display the resolved IP address in exclusion of the name the IP was resolved from. This...

Is the database column a `timestamp` or `timestamptz`? Can you make a small reproduction case for this?

Okay, I see what's going on here. The SO thread basically has the answer, but here's a little more of the explanation of why. `timestamptz` doesn't store time zones. PostgreSQL...

> @jackc I'm asking you an OPTIONAL config to return UTC as stored in DB. Please. No breaking. It already is optional. Just not with a config change. Create a...

@dedalusj I think what you would want to do is to create your own wrapper type that implements `pgtype.TimestamptzScanner` with your preferred time zone handling. Then your choice is whether...

This issue was originally filed with pgx v4. I don't see making any changes there. But think that PR https://github.com/jackc/pgx/pull/1948 would solve all the issues raised here for pgx v5....

#1948 has been merged. This should resolve this issue.