An asterisk (*) indicates support that was added in a hotfix or software patch subsequent to a release.

Refer to the following resources for additional information:

• Product Compatibility Guide: Provides the latest data source and platform support information. 
• Fixes: Describes the issues resolved since general availability.  

Version 6.0.0

ENHANCEMENTS

• The driver has been enhanced to support MERGE against PostgreSQL 15 and later. MERGE is a SQL command that modifies rows in the target table using the data from the source table. It can conditionally INSERT, UPDATE or DELETE rows in a single statement, eliminating the need to write multiple procedural statements.*
  • Available: Driver version 6.0.0.001277 (F002097.U001111)
• The driver has been enhanced to support the Geometry data type.*
  • Available: Driver version 6.0.0.001097 (F001813.U000919)
  Refer to Data types for details.
• The installer program has been enhanced to support Azul Zulu JRE 11. As a result of this change, the installer has ended support for some of the old operating systems. The installer supports the following operating systems after the enhancement:*
  • UNIX/Linux:
    • Any operating system on a machine using a JRE that is Java SE 8 or higher (LTS version), including Oracle JDK, OpenJDK, and IBM SDK (Java) distributions.
  • Windows:
    • Windows 8.1 or higher
    • Windows Server 2012 RC2 or higher
  Important: These changes do not affect the operating system requirements of the driver.
  
• The driver has been enhanced with the new EnablePrepareThreshold and 
  PrepareThreshold connection properties, which allow you to configure the 
  behavior of server-side prepared statements. Refer to the user's guide for 
  details. Refer to EnablePrepareThreshold and PrepareThreshold for details.*
• The driver has been enhanced to support stored procedures.
• The CallEscapeBehavior connection property has been added to the driver. It determines whether the driver calls a user-defined function or a stored procedure. Refer to CallEscapeBehavior for details.
• The driver has been enhanced to support the following types of data types:
  • Geometric types
  • Network address types
  • Monetary types
  • Date/time types
  • Range types
  Refer to Data types for details.
• The driver has been enhanced to support the TXID_SNAPSHOT data type. Refer to Data types for details.
• The driver has been enhanced to support the SCRAM-SHA-256 authentication method, which uses a hashing mechanism for encrypting passwords to establish a secure connection with PostgreSQL. 
• The driver has been enhanced to include timestamp in the Spy and JDBC packet
  logs by default. If required, you can disable the timestamp logging by
  specifying the following at connection: For Spy logs, set
  spyAttributes=(log=(file)Spy.log;timestamp=no) and for JDBC packet logs,
  set ddtdbg.ProtocolTraceShowTime=false.
• Interactive SQL for JDBC (JDBCISQL) is now installed with the product. JDBCISQL is a command-line interface that supports connecting your driver to a data source, executing SQL statements and retrieving results in a terminal. This tool provides a method to quickly test your drivers in an environment that does not support GUIs.
• The driver has been enhanced to support a customized version of the PostgreSQL COPY command. It provides an additional keyword, LOCALFILE, to allow you to copy data from or to standard file-system files that are stored anywhere on your network, not just on the database server. For details, refer to Using COPY command.
• The driver has been enhanced to support the PostgreSQL COPY command for batch inserts. When BatchMechanism is set to copy, the driver leverages the PostgreSQL COPY command for substantial performance gains. For details, refer to Using COPY command.
• The driver has been enhanced to support retrieving the values of auto-generated keys. For details, refer to Auto-generated keys support.
• The driver has been enhanced to support the following data types: Citext, JSON, JSONB, and UUID. Refer to Data types for details
• The driver has been enhanced to support the Kerberos authentication protocol with the following connection properties:
  • AuthenticationMethod
  • ServicePrincipalName
  Refer to Kerberos authentication for details.
• The ExtendedColumnMetadata connection property has been added to the driver. This property determines how the driver returns column metadata when retrieving results with ResultSetMetaData methods. Refer to ExtendedColumnMetadata for details.
• The RegisterStatementPoolMonitorMBean connection property has been added to the driver. Note that the driver no longer registers the Statement Pool Monitor as a JMX MBean by default. You must set RegisterStatementPoolMonitorMBean to true to register the Statement Pool Monitor and manage statement pooling with standard JMX API calls. Refer to RegisterStatementPoolMonitorMBean for details.

CHANGED BEHAVIOR

• The default value for the SupportsCatalogs connection property has been changed to true. Refer to SupportsCatalogs for details.

Version 5.1.4

ENHANCEMENTS

• The CryptoProtocolVersion connection property has been added to the driver. This property can be used to avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE vulnerability.
  
• Support for result set holdability has been added to the driver.

Version 5.1.2

ENHANCEMENTS

• Added SupportsCatalogs connection property, which enables driver support for catalog calls
• Added four connection properties to handle VARCHAR, LONGVARCHAR, and NUMERIC data types: MaxVarcharSize, MaxLongVarcharSize, MaxNumericPrecision, and MaxNumericScale

Version 5.1.1

GA Release Features

• Supports SQL access to PostgreSQL
• Supports SSL protocol for sending encrypted data
• Supports connection pooling
• Supports the DataDirect Bulk Load API
• Includes the TransactionErrorBehavior connection property which determines how the driver handles errors that occur within a transaction
• Includes the LoginTimeout connection property which allows you to specify the amount of time the driver waits for a connection to be established before timing out the connection request