Skip to:
See this for details:
http://archives.postgresql.org/pgsql-jdbc/2006-01/msg00115.php
When connection pooling is used (e.g.: c3p0, which is used in trunk), the problem does not show itself.
version: 42.2.1
loader.LaunchedURLClassLoader@61832929`---[16213.33983ms] org.postgresql.core.v3.QueryExecutorImpl:processResults()+---[min=4.39E-4ms,max=15845.548241ms,total=15845.718804ms,count=305] org.postgresql.core.PGStream:receiveChar() #1936+---[0.002326ms] org.postgresql.core.PGStream:receiveInteger4() #1943+---[0.002463ms] java.util.Deque:removeFirst() #1945
we're doing pooling everywhere now, AFAIK; marking as invalid
feel free to reopen if I'm mistaken
See this for details:
http://archives.postgresql.org/pgsql-jdbc/2006-01/msg00115.php
When connection pooling is used (e.g.: c3p0, which is used in trunk), the problem does not show itself.