Jack Christensen

> I think it’s the same result on your machine Actually, nothing printed for me. I had to change the loop to `100000` to get any output. ``` err: context...

Would it be better to instantiate a `CopyDoneResult` internally to resolve the bug rather than change the signature of the function? In theory, that's a breaking change... though I suppose...

The idea seems reasonable. Here's a few thoughts: * I would expect the type definition for `AcquireTracer` would be defined in `pgxpool` not `pgx` package. * I'm not sure about...

@ngavinsir I do not know of anyone working on this.

As of `v5.5.3`, when there is no way to encode a value in binary format, but there is a way to encode it in text format (for example `[][]string` into...

I agree that it does not exactly represent the underlying PostgreSQL array. However, even a single-dimensional array is not represented exactly. Your desired result does not exactly represent the results...

Did you read all the rows of the Query response before checking `rows.Err`?

@shkvoretz > it would've been cool to be able to check for it before reading all the rows. Some errors can be available before reading rows, but not all. This...

That's not very much information to diagnose the issue, but two things jump out at me. 1. The name "lrupsc_1_20" looks like something created by an old version of pgx....

I think that would work. Only thing to watch out for is ambiguous values that can't be round-tripped or things that don't have an obvious JSON representation. That has been...