The following bug has been logged online:

Bug reference: 2856
Logged by: Steve Langridge
Email address: steve@vanrhynsdorp.co.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.

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

On Fri, 22 Dec 2006, Steve Langridge wrote:

> Bug reference: 2856
> PostgreSQL version: 8.2
> 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).
>

I'm not sure it's legal to simply ignore the fact that the method is not
implemented. I think at minimum we'd need to keep the client info data in
the Connection object even if we don't send it to the database. This
would make it look like it was working to the JVM there just wouldn't be a
way to get at it on the database side.

Kris Jurka

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

On Fri, 5 Jan 2007, Steve Langridge wrote:

> At the present time, I am not really interested in actually using the client
> info data at all - I really just need the getClientInfo() and setClientInfo()
> to rather not raise a not-implemented exception. With the JDBC 3 driver
> under Java 1.5, there were no problems, so I presume these methods were
> implemented - it is now a real hassle since when running under Java 1.6, one
> has to use the JDBC 4 driver.
>

These methods are new in JDBC 4 which is why it wasn't a problem with JDBC
3. I understand that all you want is not to error, but I don't think
that's appropriate behavior for all users.

Kris Jurka



---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match