Connecting to the Database

With JDBC, a database is represented by a URL (Uniform Resource Locator). With PostgreSQL, this takes one of the following forms:

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

The parameters have the following meanings:

  • host

    The host name of the server. Defaults to localhost. To specify an IPv6 address your must enclose the host parameter with square brackets, for example:


  • port

    The port number the server is listening on. Defaults to the PostgreSQL™ standard port number (5432).

  • database

    The database name. The default is to connect to a database with the same name as the user name.

To connect, you need to get a Connection instance from JDBC. To do this, you use the DriverManager.getConnection() method:

Connection db = DriverManager.getConnection(url, username, password);

Connection Parameters

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. The following examples illustrate the use of both methods to establish a SSL connection.

String url = "jdbc:postgresql://localhost/test";
Properties props = new Properties();
Connection conn = DriverManager.getConnection(url, props);

String url = "jdbc:postgresql://localhost/test?user=fred&password=secret&ssl=true";
Connection conn = DriverManager.getConnection(url);
  • user = String

    The database user on whose behalf the connection is being made.

  • password = String

    The database user's password.

  • ssl = boolean

    Connect using SSL. The driver must have been compiled with SSL support. This property does not need a value associated with it. The mere presence of it specifies a SSL connection. However, for compatibility with future versions, the value "true" is preferred. For more information see Chapter 4, Using SSL.

  • sslfactory = String

    The provided value is a class name to use as the SSLSocketFactory when establishing a SSL connection. For more information see the section called “Custom SSLSocketFactory”.

  • sslfactoryarg = String

    This value is an optional argument to the constructor of the sslfactory class provided above. For more information see the section called “Custom SSLSocketFactory”.

  • sslmode = String

    possible values are "verify-ca" and "verify-full" setting these will necessitate storing the server certificate on the client machine "Configuring the client".

  • sslcert = String

    Provide the full path for the certificate file. Defaults to /defaultdir/postgresql.crt

    Note: defaultdir is ${user.home}/.postgresql/ in *nix systems and %appdata%/postgresql/ on windows

  • sslkey = String

    Provide the full path for the key file. Defaults to /defaultdir/postgresql.pk8

  • sslrootcert = String

    File name of the SSL root certificate. Defaults to defaultdir/root.crt

  • sslhostnameverifier = String

    Class name of hostname verifier. Defaults to using org.postgresql.ssl.jdbc4.LibPQFactory.verify()

  • sslpaswordcallback = String

    Class name of the SSL password provider. Defaults to org.postgresql.ssl.jdbc4.LibPQFactory.ConsoleCallbackHandler

  • sslpassword = String

    If provided will be used by ConsoleCallbackHandler

  • sendBufferSize = int

    Sets SO_SNDBUF on the connection stream

  • recvBufferSize = int

    Sets SO_RCVBUF on the connection stream

  • protocolVersion = int

    The driver supports the V3 frontend/backend protocols. The V3 protocol was introduced in 7.4 and the driver will by default try to connect using the V3 protocol.

  • loggerLevel = String

    Logger level of the driver. Allowed values: OFF, DEBUG or TRACE. This enable the java.util.logging.Logger Level of the driver based on the following mapping of levels: DEBUG -> FINE, TRACE -> FINEST. This property is intented for debug the driver and not for general SQL query debug.

  • loggerFile = String

    File name output of the Logger. If set, the Logger will use a java.util.logging.FileHandler to write to a specified file. If the parameter is not set or the file can’t be created the java.util.logging.ConsoleHandler will be used instead. This parameter should be use together with loggerLevel.

  • allowEncodingChanges = boolean

    When using the V3 protocol the driver monitors changes in certain server configuration parameters that should not be touched by end users. The client_encoding setting is set by the driver and should not be altered. If the driver detects a change it will abort the connection. There is one legitimate exception to this behaviour though, using the COPY command on a file residing on the server's filesystem. The only means of specifying the encoding of this file is by altering the client_encoding setting. The JDBC team considers this a failing of the COPY command and hopes to provide an alternate means of specifying the encoding in the future, but for now there is this URL parameter. Enable this only if you need to override the client encoding when doing a copy.

  • logUnclosedConnections = boolean

    Clients may leak Connection objects by failing to call its close() method. Eventually these objects will be garbage collected and the finalize() method will be called which will close the Connection if caller has neglected to do this himself. The usage of a finalizer is just a stopgap solution. To help developers detect and correct the source of these leaks the logUnclosedConnections URL parameter has been added. It captures a stacktrace at each Connection opening and if the finalize() method is reached without having been closed the stacktrace is printed to the log.

  • autoCloseUnclosedStatements = boolean

    Clients may leak Statement objects by failing to call its close() method. If autoCloseUnclosedStatements is set to "true" then finalizer will be used as a stopgap solution to close() the resource.

    Note: Creating finalizable objects is very expensive in lots of JVM. It dramatically impacts Statement instantiation and increases time spent in garbage collection, so avoid using autoCloseUnclosedStatements="true" for highly loaded applications unless you are sure your JVM can crater finalizer traffic.

  • binaryTransferEnable = String

    A comma separated list of types to enable binary transfer. Either OID numbers or names.

  • binaryTransferDisable = String

    A comma separated list of types to disable binary transfer. Either OID numbers or names. Overrides values in the driver default set and values set with binaryTransferEnable.

  • prepareThreshold = int

    Determine the number of PreparedStatement executions required before switching over to use server side prepared statements. The default is five, meaning start using server side prepared statements on the fifth execution of the same PreparedStatement object. More information on server side prepared statements is available in the section called “Server Prepared Statements”.

  • preparedStatementCacheQueries = int

    Determine the number of queries that are cached in each connection. The default is 256, meaning if you use more than 256 different queries in prepareStatement() calls, the least recently used ones will be discarded. The cache allows application to benefit from “Server Prepared Statements” (see prepareThreshold) even if the prepared statement is closed after each execution. The value of 0 disables the cache.

    N.B.Each connection has its own statement cache.

  • preparedStatementCacheSizeMiB = int

    Determine the maximum size (in mebibytes) of the prepared queries cache (see preparedStatementCacheQueries). The default is 5, meaning if you happen to cache more than 5 MiB of queries the least recently used ones will be discarded. The main aim of this setting is to prevent OutOfMemoryError. The value of 0 disables the cache.

  • defaultRowFetchSize = int

    Determine the number of rows fetched in ResultSet by one fetch with trip to the database. Limiting the number of rows are fetch with each trip to the database allow avoids unnecessary memory consumption and as a consequence OutOfMemoryException.

    The default is zero, meaning that in ResultSet will be fetch all rows at once. Negative number is not available.

  • loginTimeout = int

    Specify how long to wait for establishment of a database connection. The timeout is specified in seconds.

  • connectTimeout = int

    The timeout value used for socket connect operations. If connecting to the server takes longer than this value, the connection is broken. The timeout is specified in seconds and a value of zero means that it is disabled.

  • socketTimeout = int

    The timeout value used for socket read operations. If reading from the server takes longer than this value, the connection is closed. This can be used as both a brute force global query timeout and a method of detecting network problems. The timeout is specified in seconds and a value of zero means that it is disabled.

  • tcpKeepAlive = boolean

    Enable or disable TCP keep-alive probe. The default is false.

  • unknownLength = int

    Certain postgresql types such as TEXT do not have a well defined length. When returning meta-data about these types through functions like ResultSetMetaData.getColumnDisplaySize and ResultSetMetaData.getPrecision we must provide a value and various client tools have different ideas about what they would like to see. This parameter specifies the length to return for types of unknown length.

  • stringtype = String

    Specify the type to use when binding PreparedStatement parameters set via setString(). If stringtype is set to VARCHAR (the default), such parameters will be sent to the server as varchar parameters. If stringtype is set to unspecified, parameters will be sent to the server as untyped values, and the server will attempt to infer an appropriate type. This is useful if you have an existing application that uses setString() to set parameters that are actually some other type, such as integers, and you are unable to change the application to use an appropriate method such as setInt().

  • kerberosServerName = String

    The Kerberos service name to use when authenticating with GSSAPI. This is equivalent to libpq's PGKRBSRVNAME environment variable and defaults to "postgres".

  • jaasApplicationName = String

    Specifies the name of the JAAS system or application login configuration.

  • ApplicationName = String

    Specifies the name of the application that is using the connection. This allows a database administrator to see what applications are connected to the server and what resources they are using through views like pgstatactivity.

  • gsslib = String

    Force either SSPI (Windows transparent single-sign-on) or GSSAPI (Kerberos, via JSSE) to be used when the server requests Kerberos or SSPI authentication. Permissible values are auto (default, see below), sspi (force SSPI) or gssapi (force GSSAPI-JSSE).

    If this parameter is auto, SSPI is attempted if the server requests SSPI authentication, the JDBC client is running on Windows, and the Waffle libraries required for SSPI are on the CLASSPATH. Otherwise Kerberos/GSSAPI via JSSE is used. Note that this behaviour does not exactly match that of libpq, which uses Windows' SSPI libraries for Kerberos (GSSAPI) requests by default when on Windows.

    gssapi mode forces JSSE's GSSAPI to be used even if SSPI is available, matching the pre-9.4 behaviour.

    On non-Windows platforms or where SSPI is unavailable, forcing sspi mode will fail with a PSQLException.

    Since: 9.4

  • sspiServiceClass = String

    Specifies the name of the Windows SSPI service class that forms the service class part of the SPN. The default, POSTGRES, is almost always correct.

    See: SSPI authentication (Pg docs) Service Principal Names (MSDN), DsMakeSpn (MSDN) Configuring SSPI (Pg wiki).

    This parameter is ignored on non-Windows platforms.

  • useSpnego = boolean

    Use SPNEGO in SSPI authentication requests

  • sendBufferSize = int

    Sets SO_SNDBUF on the connection stream

  • receiveBufferSize = int

    Sets SO_RCVBUF on the connection stream

  • readOnly = boolean

    Put the connection in read-only mode

  • disableColumnSanitiser = boolean

    Enable optimization that disables column name sanitiser.

  • assumeMinServerVersion = String

    Assume that the server is at least the given version, thus enabling to some optimization at connection time instead of trying to be version blind.

  • currentSchema = String

    Specify the schema to be set in the search-path. This schema will be used to resolve unqualified object names used in statements over this connection.

  • targetServerType = String

    Allows opening connections to only servers with required state, the allowed values are any, master, slave and preferSlave. The master/slave distinction is currently done by observing if the server allows writes. The value preferSlave tries to connect to slaves if any are available, otherwise allows falls back to connecting also to master.

  • hostRecheckSeconds = int

    Controls how long in seconds the knowledge about a host state is cached in JVM wide global cache. The default value is 10 seconds.

  • loadBalanceHosts = boolean

    In default mode (disabled) hosts are connected in the given order. If enabled hosts are chosen randomly from the set of suitable candidates.

  • socketFactory = String

    The provided value is a class name to use as the SocketFactory when establishing a socket connection. This may be used to create unix sockets instead of normal sockets. The class name specified by socketFactory must extend and be available to the driver's classloader. This class must have a zero argument constructor or a single argument constructor taking a String argument. This argument may optionally be supplied by socketFactoryArg.

  • socketFactoryArg = String

    This value is an optional argument to the constructor of the socket factory class provided above.

  • reWriteBatchedInserts = boolean

    This will change batch inserts from insert into foo (col1, col2, col3) values (1,2,3) into insert into foo (col1, col2, col3) values (1,2,3), (4,5,6) this provides 2-3x performance improvement

    Connection Fail-over

    To support simple connection fail-over it is possible to define multiple endpoints (host and port pairs) in the connection url separated by commas. The driver will try to once connect to each of them in order until the connection succeeds. If none succeed, a normal connection exception is thrown.

    The syntax for the connection url is:


    The simple connection fail-over is useful when running against a high availability postgres installation that has identical data on each node. For example streaming replication postgres or postgres-xc cluster.

    For example an application can create two connection pools. One data source is for writes, another for reads. The write pool limits connections only to master node:

    jdbc:postgresql://node1,node2,node3/accounting?targetServerType=master. And read pool balances connections between slaves nodes, but allows connections also to master if no slaves are available:


Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group