Development Specifications

If the connection pool mechanism is used during application development, comply with the following specifications:

If GUC parameters are set in the connection, run SET SESSION AUTHORIZATION DEFAULT;RESET ALL; to clear the connection status before you return the connection to the connection pool.
If a temporary table is used, delete the temporary table before you return the connection to the connection pool.

If you do not do so, the connection in the connection pool will be stateful, which affects subsequent operations on the connection pool.

Compatibility:

The new driver is forward compatible with the database. To use the new features added to the driver and database, you must upgrade the database.
Setting behavior_compat_options to 'proc_outparam_override' is applicable only in A-compatible mode.

If the driver is used in a multi-thread environment:

The JDBC driver is not thread-safe and does not guarantee that the connection methods are synchronized. The caller synchronizes the calls to the driver.

Table 1 describes the compatibility of application development drivers.

**Table 1** Description of compatibility
Driver	Compatibility
JDBC and Go	The driver is forward compatible with earlier database versions. However, to use the new features added to the driver and database, you must upgrade the database.
ODBC, libpq, and Psycopg	The driver version must match the database version.