Progress DataDirect for JDBC for PostgreSQL Driver
An asterisk (*) indicates support that was added in a hotfix or software patch subsequent to a release.
For a list a list of issues resolved since general availability, refer to the fixes.
Certified with Google AlloyDB for PostgreSQL* Driver version 6.0.0.001023 (F001717.U000848)
Certified with Yellowbrick Data Warehouse* Driver version 6.0.0.000478 (F001356.U000687)
Certified with PostgreSQL 14* Driver version 6.0.0.000318 (F001235.U000640)
The driver has been enhanced to support the Geography data type.
Available: Driver version 6.0.0.001097 (F001813.U000919)
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:*
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 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.*
The driver has been enhanced to support stored procedures for PostgreSQL 11 and later.
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 the user's guide for details.
The driver has been enhanced to support the following types of data types:
Network address types
The driver has been enhanced to support the TXID_SNAPSHOT data type.
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 (v10.0 and higher). This method requires a Java Virtual Machine
(JVM) that is Java SE 8 or higher.
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 the user's guide.
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.
The driver has been enhanced to support retrieving the values of auto-generated keys.
The driver has been enhanced to support the following data types: Citext, JSON, JSONB, and UUID.
The driver has been enhanced to support the Kerberos authentication protocol with the following connection properties:
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.
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.
The default value for the SupportsCatalogs connection property has been changed to true.
Java SE 7 has reached the end of its product life cycle and will no longer receive generally available security updates. As a result, the drivers will no longer support JVMs that are version Java SE 7 or earlier. Support for distributed versions
of Java SE 7 and earlier will also end, including IBM SDK (Java Edition).
Certified with PostgreSQL 13* Driver version 5.1.4.000284 (F000495.U000247)
Certified with PostgreSQL 12* Driver version 5.1.4.000244 (F000453.U000216)
Certified with PostgreSQL 11* Driver version 5.1.4.000134 (F000378.U000183)
Certified with Oracle JDK 11* Driver version 5.1.4.000134 (F000378.U000183)
Certified with OpenJDK 11* Driver version 5.1.4.000134 (F000378.U000183)
Certified with OpenJDK 8 on Windows and Linux* Driver version 5.1.4.000134 (F000378.U000183)
Certified with Amazon Aurora PostgreSQL 1.0* Driver version 5.1.4.000130 (F000375.U000182)
Certified with EDB Postgres Advanced Server 10.1* Driver version 5.1.4.000130 (F000375.U000182)
Certified with PostgreSQL 10.1* Driver version 5.1.4.000121 (F000358.U000177)
Certified with PostgreSQL 9.5 and 9.6*
Certified with PostgreSQL 9.3 and 9.4
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.
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
GA Release Features
Supports SQL access to PostgreSQL 8.2 and higher
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