Jack Christensen

I'm open to this being changed.

I'm not sure tagging a version of pgerrcode for each PG version is the best approach. It is quite likely some users of pgerrcode will connect to multiple different versions...

You've got a lot of functionality in those packages. Just out of curiosity, what's the domain you're working in? --- As far as adding more public interfaces, I can see...

I'm not sure I understand the use case. In your example I would expect you to call `Scan` and handle the returned error. The reason `errRows` has an `Err()` method...

This change won't do what you want. And what you are doing with `Query()` isn't reliable either. `Query()` will only return an error in limited circumstances such as a network...

The performance gain by using `LoadTypes` is primarily saving on the network round trips. If you are on a fast link, it may not make much difference. But I still...

> I'm seeing this log entry getting called a lot, and customTypeExists is always false. So I'm thinking that maybe I've not wired this up the best way or something....

This approach would work in the overwhelming majority of cases, but there is the potential for some nasty edge cases. 1. DDL that is executed after the pool was created...

Are there any recoverable errors beside `conn busy`? I'd consider `conn busy` to be a bug in the application code.

You need to check `rows.Err()` after the `rows.Next()` loop completes.