BUG #2856: Jdbc 4 connector running on JDK 1.6 should not raise exception for getClientInfo/setClientInfo

The following bug has been logged online:

Bug reference: 2856
Logged by: Steve Langridge
Email address: steve(at)vanrhynsdorp(dot)co(dot)za
PostgreSQL version: 8.2
Operating system: Windows XP Pro SP2
Description: Jdbc 4 connector running on JDK 1.6 should not raise
exception for getClientInfo/setClientInfo
Details:

When using the Jdbc 4 driver running on Java 1.6, it would be preferable if
the methods getClientInfo() and setClientInfo() returned silently, instead
of raising an exception about not being implemented. When running on
Glassfish with Toplink Essentials, the app server log gets filled with these
exceptions for every access from a JDBC connection pool (when using the
PGConnectionPoolDataSource).

This has been discussed on the Nabble forums, but I do not see that it has
been posted anywhere on the Postgres forums.

Regards,

Steve.