> On 13 Dec 2024, at 13:56, David Gradwell <david(at)gradwell(dot)com> wrote:
> This is 100% reproducible in many Java applications. Reverting the application build to using postgresql-42.5.4.jar and the problem goes away.
While there are JDBC maintainers on the postgres lists, it's better to report
JDBC issues directly to the JDBC project:
https://github.com/pgjdbc/pgjdbc/issues
--
Daniel Gustafsson