Jack Christensen

Maybe take a look at the CI for pgxutil. It is a simple CI setup that uses pgx and works in Github Actions. https://github.com/jackc/pgxutil/blob/master/.github/workflows/ci.yml

It's a good thing you brought up the broken statement issue. Somehow I'd totally forgotten that issue in only a week 🤦 . The error is silent because the SQL...

There will probably be a new release in the next couple weeks. But for now you can use a specific commit like this: ``` go get github.com/jackc/pgx/v5@304697de36f37f92f8ad7b6eeb5061ea66324d3d ```

Would these comments be static per query or would they be embedding dynamic values like a request ID? Dynamic values would make prepared statements ineffective (and pgx automatically prepares and...

Based on the SQL you have, it looks like the problem is the where clause is being applied to the children as well as the root nodes when it should...

It would be cool, but I think it may be harder than it initially appears. For example, given the approach of trying a recursive query and recovering on error. What...

This seems to have broken a couple tests. Not immediately obvious why. But even without that I'm not sure if this is the right approach. I would expect it to...

This is probably related to https://github.com/jackc/pgx/pull/1629. Previously, `CheckConn` did a non-blocking read syscall. However, that system had a number of fundamental issues. Now, it does a normal read with a...

As of cf6ef75f916648857cf7b46322d6d7af7d372917, stdlib uses `Ping` instead of the deprecated `CheckConn`. This should resolve the issue. In addition, on a local network it should be faster.

`CustomCancel` was removed in v4 because v4 changed strategies for context cancellation from cancelling the in progress query and attempting to recover to just closing the connection. So there was...