PostgreSQL JDBC Driver (PgJDBC for short) allows Java programs to connect to a PostgreSQL database using standard, database independent Java code. Is an open source JDBC driver written in Pure Java (Type 4), and communicates in the PostgreSQL native network protocol.

The current version of the driver should be compatible with PostgreSQL 8.2 and higher using the version 3.0 of the protocol, and Java 6 (JDBC 4.0), Java 7 (JDBC 4.1) and Java 8 (JDBC 4.2). Unless you have unusual requirements (running old applications or JVMs), this is the driver you should be using.

PgJDBC regression tests are run against all PostgreSQL versions since 8.2, including "build PostgreSQL from git master" version. There are other derived forks of PostgreSQL but have not been certified to run with PgJDBC. If you find a bug or regression on supported versions, please fill an Issue.

Most people do not need to compile PgJDBC. You can download the precompiled driver (jar) from the PostgreSQL JDBC site or using your chosen dependency management tool:

You can search on The Central Repository with GroupId and ArtifactId for:

<dependency>
    <groupId>org.postgresql</groupId>
    <artifactId>postgresql</artifactId>
    <version>42.1.3</version>
</dependency>

<dependency>
    <groupId>org.postgresql</groupId>
    <artifactId>postgresql</artifactId>
    <version>42.1.3.jre7</version>
</dependency>

<dependency>
    <groupId>org.postgresql</groupId>
    <artifactId>postgresql</artifactId>
    <version>42.1.3.jre6</version>
</dependency>

Snapshot builds (builds from master branch) are also deployed to Maven Central, so you can test current development version (test some bugfix) using:

<dependency>
  <groupId>org.postgresql</groupId>
  <artifactId>postgresql</artifactId>
  <version>42.2.0-SNAPSHOT</version> <!-- Java 8 -->
  <version>42.2.0.jre7-SNAPSHOT</version> <!-- Java 7 -->
  <version>42.2.0.jre6-SNAPSHOT</version> <!-- Java 6 -->
</dependency>

There are also available (snapshot) binary RPMs in Fedora's Copr repository.

Notable changes for:

42.1.3 (2017-07-14):

• fixed NPE in PreparedStatement.executeBatch in case of empty batch (regression since 42.1.2) PR#867

42.1.2 (2017-07-12):

• Better logic for returning keyword detection. Previously, pgjdbc could be defeated by column names that contain returning, so pgjdbc failed to "return generated keys" as it considered statement as already having returning keyword PR#824 201daf1d
• Replication API: fix issue #834 setting statusIntervalUpdate causes high CPU load PR#835 59236b74
• perf: use server-prepared statements for batch inserts when prepareThreshold>0. Note: this enables batch to use server-prepared from the first executeBatch() execution (previously it waited for prepareThreshold executeBatch() calls) abc3d9d7

42.1.1 (2017-05-05):

• fix: infinite dates might be corrupted when transferred in binary for certain JREs. For instance, 5881610-07-11 instead of infinity.

42.1.0 (2017-05-04):

• fix: data being trucated in setCharacterStream (the bug introduced in 42.0.0) PR#802
• fix: calculation of lastReceiveLSN for logical replication PR#801
• fix: make sure org.postgresql.Driver is loaded when accessing though DataSource interface #768
• feat: support fetching a REF_CURSOR using getObject PR#809
• note: there's no 42.1.0.jre6 due to infinity handling bug. Fixed in 42.1.1.jre6

42.0.0 (2017-02-20):

• Support for PostgreSQL versions below 8.2 was dropped
• java.util.logging is now used for logging: logging documentation
• Ensure executeBatch() can be used with pgbouncer. Previously pgjdbc could use server-prepared statements for batch execution even with prepareThreshold=0 (see issue 742)
• Replication protocol API was added: replication API documentation, GitHub PR 550
• Version bumped to 42.0.0 to avoid version clash with PostgreSQL version
• Error position is displayed when SQL has unterminated literals, comments, etc (see issue 688)

9.4.1212 (2016-11-02):

• ? can now be used in non-prepared statements (fixed regression of 9.4.1210)

9.4.1211 (2016-09-18):

• json type is returned as PGObject like in pre-9.4.1210 (fixed regression of 9.4.1210)
• 'current transaction is aborted' exception includes the original exception via caused-by chain

9.4.1210 (2016-09-07):

• BUG: json datatype is returned as java.lang.String object, not as PGObject (fixed in 9.4.1211)
• Better support for RETURN_GENERATED_KEYS, statements with RETURNING clause
• Avoid user-visible prepared-statement errors if client uses DEALLOCATE/DISCARD statements (invalidate cache when those statements detected)
• Avoid user-visible prepared-statement errors if client changes search_path (invalidate cache when set search_path detected)
• Support comments when replacing {fn ...} JDBC syntax
• Support for Types.REF_CURSOR

9.4.1209 (2016-07-15):

• Many improvements to insert into .. values(?,?) => insert .. values(?,?), (?,?)... rewriter. Give it a try by using reWriteBatchedInserts=true connection property. 2-3x improvements for insert batch can be expected
• Full test suite passes against PostgreSQL 9.6, and OpenJDK 9
• Performance optimization for timestamps (~TimeZone.getDefault optimization)
• Allow build-from-source on GNU/Linux without maven repositories, and add Fedora Copr test to the regression suite

Read the History of Changes for reference of previous versions.

For more information you can read the PgJDBC driver documentation or for general JDBC documentation please refer to The Java™ Tutorials.

The driver recognises JDBC URLs of the form:

jdbc:postgresql:database
jdbc:postgresql:/
jdbc:postgresql://host/database
jdbc:postgresql://host/
jdbc:postgresql://host:port/database
jdbc:postgresql://host:port/

The general format for a JDBC URL for connecting to a PostgreSQL server is as follows, with items in square brackets ([ ]) being optional:

jdbc:postgresql://[host][:port][/[database]][?property1=value1[&property2=value2]...]

where:

• jdbc:postgresql: (Required) is known as the sub-protocol and is constant.
• host (Optional) is the server address to connect. This could be a DNS or IP address, or it could be localhost or 127.0.0.1 for the local computer. To specify an IPv6 address your must enclose the host parameter with square brackets (jdbc:postgresql://[::1]:5740/accounting). Defaults to localhost.
• port (Optional) is the port number listening on the host. Defaults to 5432.
• database (Optional) is the database name. Defaults to the same name as the user name used in the connection.
• propertyX (Optional) is one or more option connection properties. For more information see Connection properties.

In addition to the standard connection parameters the driver supports a number of additional properties which can be used to specify additional driver behaviour specific to PostgreSQL™. These properties may be specified in either the connection URL or an additional Properties object parameter to DriverManager.getConnection.

For information on how to contribute to the project see the Contributing Guidelines

• PostgreSQL International
• YourKit