pgjdbc/pgjdbc

Bidirectional TCP streams aren’t perfect. There’s a deadlock-avoidance mechanism that can become a real hotspot with pipelining (obviously), and with batch updates that return values (less obvious).

No repro needed. A one-line reply is enough, and I'm happy to file the issue for you, or to help you file it. Same for the other direction: if there's behavior you rely on and would hate to see…

In 2022 I wrote the right design into the issue myself: "the cache should be like query + currentParameterTypes => actualParameterTypes". Then I didn't build it. My WIP branch cached the wrong thing.…

Also, for maintainers: cutting a release used to mean editing several config files in lockstep, and we got it wrong a few times. Now adding the version's release notes is enough — the rest of the…

Wrapping up Struct/Array/SQLData + pluggable codecs in pgjdbc: Binary codecs for composites and arrays should be a meaningful perf win over the old text-only path. WIP, but in good shape — would love…