I didn’t know you already reported it. Anyway it might be good to remind Postgres guys about the problem. This issue is major and it's really hard to believe that this hasn’t been covered since 2011. I wonder how many developers will waste their time debugging Apache DBCP or other framework, only to find out that issue lies inside JDBC.