http://jdbc.postgresql.org/changes.htmlJDBC Driver Changesen-ushttp://jdbc.postgresql.org/changes.html fix by jurka : When doing batch execution we can have multiple Parse and DescribeStatement messages on the wire at the same time. When we finally get around to collecting the DescribeStatement results we must check whether they still apply to the currently parsed query. Otherwise we'll overwrite our type information with stale data that will cause failures down the line. Thanks to Eric Faulhaber.http://jdbc.postgresql.org/changes.html add by jurka : Provide a minimal ClientInfo implementation because of complaints about exceptions continually being thrown on glassfish. http://jdbc.postgresql.org/changes.html add by jurka : Set extra_float_digits=2 on connection startup so we get as much data about floats as possible. http://jdbc.postgresql.org/changes.html update by jurka : Assorted cleanups to the source tree based on findbugs output. Thanks to Mikko Tiihonen.http://jdbc.postgresql.org/changes.html fix by jurka : CallableStatements with OUT parameters that get executed more than prepareThreshold times failed if clearParameters() was called in between executions. When we've hit the prepareThreshold, we no longer send Parse messages which invoke SimpleParameterList.getTypeOID which has side effects required to setup the parameters correctly. Add an explicit convertFunctionOutParameters method to do this work instead that we call in all execution paths. Thanks to Ludovico Bianchini.http://jdbc.postgresql.org/changes.html fix by jurka : The driver was incorrectly parsing identifiers that had parts that look like dollar quotes. Things like a$b$c are valid identifiers, not dollar quotes. When determining if a $ we've found is a dollar quote start, look at the preceding character and see if it is a valid identifier part to determine if we're in the midst of an identifier or are starting a new token. Thanks to Michael Paesold.http://jdbc.postgresql.org/changes.html fix by jurka : Multiple calls to XAConnection.getConnection within the same user transaction ended up restarting the transaction on the server side as a result of manipulating the autocommit state. When retrieving a Connection, we must pay attention to whether a user transaction is in progress when setting the autocommit state. Thanks to Heikki Linnakangas.http://jdbc.postgresql.org/changes.html fix by jurka : Make code that parses queries for updateable resultsets aware of the ONLY clause. Thanks to Oleg Vasylenko.http://jdbc.postgresql.org/changes.html add by jurka : Support multi-dimensional arrays and returning arrays of primitive server types as wrapped java Objects so that NULL values can be detected. Backwards compatibility is provided using the compatible=8.2 URL option to return arrays of primitive types. Thanks to Marek Lewczuk.http://jdbc.postgresql.org/changes.html fix by jurka : While custom type maps are not implemented, the code to detect the caller trying to use them threw a ClassCastException. Correctly detect the attempted use of custom types and bail out with a SQLException. http://jdbc.postgresql.org/changes.html add by jurka : Implement the JDBC4 method Connection.createArrayOf. Now people can portably and easily handle array data. http://jdbc.postgresql.org/changes.html fix by jurka : When dealing with OIDs larger than 2^31 we can't retrieve these as Java ints. Using long throughout the driver would be a pain, one reason is that you can't use a switch on a long variable. PG supports representing OIDs as signed ints (select '3000000000'::oid::int4), so retrieve the values as longs, but then cast to int to get the signed representation. Thanks to Tom Lane, Quinton Dolan.