PostgreSQL

  +
  This function opens a new database connection using the parameters taken from two `+NULL+`-terminated arrays. The first, `+keywords+`, is defined as an array of strings, each one being a key word. The second, `+values+`, gives the value for each key word. Unlike link:libpq-connect.html#LIBPQ-PQSETDBLOGIN[`+PQsetdbLogin+`] below, the parameter set can be extended without changing the function signature, so use of this function (or its nonblocking analogs link:libpq-connect.html#LIBPQ-PQCONNECTSTARTPARAMS[`+PQconnectStartParams+`] and `+PQconnectPoll+`) is preferred for new application programming.
  +
  The currently recognized parameter key words are listed in link:libpq-connect.html#LIBPQ-PARAMKEYWORDS[Section 34.1.2].
  +
  The passed arrays can be empty to use all default parameters, or can contain one or more parameter settings. They must be matched in length. Processing will stop at the first `+NULL+` entry in the `+keywords+` array. Also, if the `+values+` entry associated with a non-`+NULL+` `+keywords+` entry is `+NULL+` or an empty string, that entry is ignored and processing continues with the next pair of array entries.
  +
  When `+expand_dbname+` is non-zero, the value for the first _`+dbname+`_ key word is checked to see if it is a _connection string_. If so, it is [.quote]#“[.quote]#expanded#”# into the individual connection parameters extracted from the string. The value is considered to be a connection string, rather than just a database name, if it contains an equal sign (`+=+`) or it begins with a URI scheme designator. (More details on connection string formats appear in link:libpq-connect.html#LIBPQ-CONNSTRING[Section 34.1.1].) Only the first occurrence of _`+dbname+`_ is treated in this way; any subsequent _`+dbname+`_ parameter is processed as a plain database name.
  +
  In general the parameter arrays are processed from start to end. If any key word is repeated, the last value (that is not `+NULL+` or empty) is used. This rule applies in particular when a key word found in a connection string conflicts with one appearing in the `+keywords+` array. Thus, the programmer may determine whether array entries can override or be overridden by values taken from a connection string. Array entries appearing before an expanded _`+dbname+`_ entry can be overridden by fields of the connection string, and in turn those fields are overridden by array entries appearing after _`+dbname+`_ (but, again, only if those entries supply non-empty values).
  +
  After processing all the array entries and any expanded connection string, any connection parameters that remain unset are filled with default values. If an unset parameter's corresponding environment variable (see link:libpq-envars.html[Section 34.15]) is set, its value is used. If the environment variable is not set either, then the parameter's built-in default value is used.
[.term]#`+PQconnectdb+` link:libpq-connect.html#LIBPQ-PQCONNECTDB[#]::
  Makes a new connection to the database server.
  +

  +
  This function opens a new database connection using the parameters taken from the string `+conninfo+`.
  +
  The passed string can be empty to use all default parameters, or it can contain one or more parameter settings separated by whitespace, or it can contain a URI. See link:libpq-connect.html#LIBPQ-CONNSTRING[Section 34.1.1] for details.
[.term]#`+PQsetdbLogin+` link:libpq-connect.html#LIBPQ-PQSETDBLOGIN[#]::
  Makes a new connection to the database server.
  +

  +
  This is the predecessor of link:libpq-connect.html#LIBPQ-PQCONNECTDB[`+PQconnectdb+`] with a fixed set of parameters. It has the same functionality except that the missing parameters will always take on default values. Write `+NULL+` or an empty string for any one of the fixed parameters that is to be defaulted.
  +
  If the _`+dbName+`_ contains an `+=+` sign or has a valid connection URI prefix, it is taken as a _`+conninfo+`_ string in exactly the same way as if it had been passed to link:libpq-connect.html#LIBPQ-PQCONNECTDB[`+PQconnectdb+`], and the remaining parameters are then applied as specified for link:libpq-connect.html#LIBPQ-PQCONNECTDBPARAMS[`+PQconnectdbParams+`].
  +
  `+pgtty+` is no longer used and any value passed will be ignored.
[.term]#`+PQsetdb+` link:libpq-connect.html#LIBPQ-PQSETDB[#]::
  Makes a new connection to the database server.
  +

  +
  This is a macro that calls link:libpq-connect.html#LIBPQ-PQSETDBLOGIN[`+PQsetdbLogin+`] with null pointers for the _`+login+`_ and _`+pwd+`_ parameters. It is provided for backward compatibility with very old programs.
[.term]#`+PQconnectStartParams+` +
#[.term]#`+PQconnectStart+` +
#[.term]#`+PQconnectPoll+` link:libpq-connect.html#LIBPQ-PQCONNECTSTARTPARAMS[#]::
   Make a connection to the database server in a nonblocking manner.
  +

+
These three functions are used to open a connection to a database server such that your application's thread of execution is not blocked on remote I/O whilst doing so. The point of this approach is that the waits for I/O to complete can occur in the application's main loop, rather than down inside link:libpq-connect.html#LIBPQ-PQCONNECTDBPARAMS[`+PQconnectdbParams+`] or link:libpq-connect.html#LIBPQ-PQCONNECTDB[`+PQconnectdb+`], and so the application can manage this operation in parallel with other activities.
+
With link:libpq-connect.html#LIBPQ-PQCONNECTSTARTPARAMS[`+PQconnectStartParams+`], the database connection is made using the parameters taken from the `+keywords+` and `+values+` arrays, and controlled by `+expand_dbname+`, as described above for link:libpq-connect.html#LIBPQ-PQCONNECTDBPARAMS[`+PQconnectdbParams+`].
+
With `+PQconnectStart+`, the database connection is made using the parameters taken from the string `+conninfo+` as described above for link:libpq-connect.html#LIBPQ-PQCONNECTDB[`+PQconnectdb+`].
+
Neither link:libpq-connect.html#LIBPQ-PQCONNECTSTARTPARAMS[`+PQconnectStartParams+`] nor `+PQconnectStart+` nor `+PQconnectPoll+` will block, so long as a number of restrictions are met:
+
* The `+hostaddr+` parameter must be used appropriately to prevent DNS queries from being made. See the documentation of this parameter in link:libpq-connect.html#LIBPQ-PARAMKEYWORDS[Section 34.1.2] for details.
* If you call link:libpq-control.html#LIBPQ-PQTRACE[`+PQtrace+`], ensure that the stream object into which you trace will not block.
* You must ensure that the socket is in the appropriate state before calling `+PQconnectPoll+`, as described below.
+
To begin a nonblocking connection request, call `+PQconnectStart+` or link:libpq-connect.html#LIBPQ-PQCONNECTSTARTPARAMS[`+PQconnectStartParams+`]. If the result is null, then libpq has been unable to allocate a new `+PGconn+` structure. Otherwise, a valid `+PGconn+` pointer is returned (though not yet representing a valid connection to the database). Next call `+PQstatus(conn)+`. If the result is `+CONNECTION_BAD+`, the connection attempt has already failed, typically because of invalid connection parameters.
+
If `+PQconnectStart+` or link:libpq-connect.html#LIBPQ-PQCONNECTSTARTPARAMS[`+PQconnectStartParams+`] succeeds, the next stage is to poll libpq so that it can proceed with the connection sequence. Use `+PQsocket(conn)+` to obtain the descriptor of the socket underlying the database connection. (Caution: do not assume that the socket remains the same across `+PQconnectPoll+` calls.) Loop thus: If `+PQconnectPoll(conn)+` last returned `+PGRES_POLLING_READING+`, wait until the socket is ready to read (as indicated by `+select()+`, `+poll()+`, or similar system function). Then call `+PQconnectPoll(conn)+` again. Conversely, if `+PQconnectPoll(conn)+` last returned `+PGRES_POLLING_WRITING+`, wait until the socket is ready to write, then call `+PQconnectPoll(conn)+` again. On the first iteration, i.e., if you have yet to call `+PQconnectPoll+`, behave as if it last returned `+PGRES_POLLING_WRITING+`. Continue this loop until `+PQconnectPoll(conn)+` returns `+PGRES_POLLING_FAILED+`, indicating the connection procedure has failed, or `+PGRES_POLLING_OK+`, indicating the connection has been successfully made.
+
At any time during connection, the status of the connection can be checked by calling link:libpq-status.html#LIBPQ-PQSTATUS[`+PQstatus+`]. If this call returns `+CONNECTION_BAD+`, then the connection procedure has failed; if the call returns `+CONNECTION_OK+`, then the connection is ready. Both of these states are equally detectable from the return value of `+PQconnectPoll+`, described above. Other states might also occur during (and only during) an asynchronous connection procedure. These indicate the current stage of the connection procedure and might be useful to provide feedback to the user for example. These statuses are:
+
[.term]#`+CONNECTION_STARTED+`# link:libpq-connect.html#LIBPQ-CONNECTION-STARTED[#];;
  Waiting for connection to be made.
[.term]#`+CONNECTION_MADE+`# link:libpq-connect.html#LIBPQ-CONNECTION-MADE[#];;
  Connection OK; waiting to send.
[.term]#`+CONNECTION_AWAITING_RESPONSE+`# link:libpq-connect.html#LIBPQ-CONNECTION-AWAITING-RESPONSE[#];;
  Waiting for a response from the server.
[.term]#`+CONNECTION_AUTH_OK+`# link:libpq-connect.html#LIBPQ-CONNECTION-AUTH-OK[#];;
  Received authentication; waiting for backend start-up to finish.
[.term]#`+CONNECTION_SSL_STARTUP+`# link:libpq-connect.html#LIBPQ-CONNECTION-SSL-STARTUP[#];;
  Negotiating SSL encryption.
[.term]#`+CONNECTION_SETENV+`# link:libpq-connect.html#LIBPQ-CONNECTION-SETENV[#];;
  Negotiating environment-driven parameter settings.
[.term]#`+CONNECTION_CHECK_WRITABLE+`# link:libpq-connect.html#LIBPQ-CONNECTION-CHECK-WRITABLE[#];;
  Checking if connection is able to handle write transactions.
[.term]#`+CONNECTION_CONSUME+`# link:libpq-connect.html#LIBPQ-CONNECTION-CONSUME[#];;
  Consuming any remaining response messages on connection.
+
Note that, although these constants will remain (in order to maintain compatibility), an application should never rely upon these occurring in a particular order, or at all, or on the status always being one of these documented values. An application might do something like this:
+

  +
  The `+connect_timeout+` connection parameter is ignored when using `+PQconnectPoll+`; it is the application's responsibility to decide whether an excessive amount of time has elapsed. Otherwise, `+PQconnectStart+` followed by a `+PQconnectPoll+` loop is equivalent to link:libpq-connect.html#LIBPQ-PQCONNECTDB[`+PQconnectdb+`].
  +
  Note that when `+PQconnectStart+` or link:libpq-connect.html#LIBPQ-PQCONNECTSTARTPARAMS[`+PQconnectStartParams+`] returns a non-null pointer, you must call link:libpq-connect.html#LIBPQ-PQFINISH[`+PQfinish+`] when you are finished with it, in order to dispose of the structure and any associated memory blocks. This must be done even if the connection attempt fails or is abandoned.
[.term]#`+PQconndefaults+` link:libpq-connect.html#LIBPQ-PQCONNDEFAULTS[#]::
  Returns the default connection options.
  +

  +
  Returns a connection options array. This can be used to determine all possible link:libpq-connect.html#LIBPQ-PQCONNECTDB[`+PQconnectdb+`] options and their current default values. The return value points to an array of `+PQconninfoOption+` structures, which ends with an entry having a null `+keyword+` pointer. The null pointer is returned if memory could not be allocated. Note that the current default values (`+val+` fields) will depend on environment variables and other context. A missing or invalid service file will be silently ignored. Callers must treat the connection options data as read-only.
  +
  After processing the options array, free it by passing it to link:libpq-misc.html#LIBPQ-PQCONNINFOFREE[`+PQconninfoFree+`]. If this is not done, a small amount of memory is leaked for each call to link:libpq-connect.html#LIBPQ-PQCONNDEFAULTS[`+PQconndefaults+`].
[.term]#`+PQconninfo+` link:libpq-connect.html#LIBPQ-PQCONNINFO[#]::
  Returns the connection options used by a live connection.
  +

  +
  Returns a connection options array. This can be used to determine all possible link:libpq-connect.html#LIBPQ-PQCONNECTDB[`+PQconnectdb+`] options and the values that were used to connect to the server. The return value points to an array of `+PQconninfoOption+` structures, which ends with an entry having a null `+keyword+` pointer. All notes above for link:libpq-connect.html#LIBPQ-PQCONNDEFAULTS[`+PQconndefaults+`] also apply to the result of link:libpq-connect.html#LIBPQ-PQCONNINFO[`+PQconninfo+`].
[.term]#`+PQconninfoParse+` link:libpq-connect.html#LIBPQ-PQCONNINFOPARSE[#]::
  Returns parsed connection options from the provided connection string.
  +

  +
  Parses a connection string and returns the resulting options as an array; or returns `+NULL+` if there is a problem with the connection string. This function can be used to extract the link:libpq-connect.html#LIBPQ-PQCONNECTDB[`+PQconnectdb+`] options in the provided connection string. The return value points to an array of `+PQconninfoOption+` structures, which ends with an entry having a null `+keyword+` pointer.
  +
  All legal options will be present in the result array, but the `+PQconninfoOption+` for any option not present in the connection string will have `+val+` set to `+NULL+`; default values are not inserted.
  +
  If `+errmsg+` is not `+NULL+`, then `+*errmsg+` is set to `+NULL+` on success, else to a `+malloc+`'d error string explaining the problem. (It is also possible for `+*errmsg+` to be set to `+NULL+` and the function to return `+NULL+`; this indicates an out-of-memory condition.)
  +
  After processing the options array, free it by passing it to link:libpq-misc.html#LIBPQ-PQCONNINFOFREE[`+PQconninfoFree+`]. If this is not done, some memory is leaked for each call to link:libpq-connect.html#LIBPQ-PQCONNINFOPARSE[`+PQconninfoParse+`]. Conversely, if an error occurs and `+errmsg+` is not `+NULL+`, be sure to free the error string using link:libpq-misc.html#LIBPQ-PQFREEMEM[`+PQfreemem+`].
[.term]#`+PQfinish+` link:libpq-connect.html#LIBPQ-PQFINISH[#]::
  Closes the connection to the server. Also frees memory used by the `+PGconn+` object.
  +

  +
  Note that even if the server connection attempt fails (as indicated by link:libpq-status.html#LIBPQ-PQSTATUS[`+PQstatus+`]), the application should call link:libpq-connect.html#LIBPQ-PQFINISH[`+PQfinish+`] to free the memory used by the `+PGconn+` object. The `+PGconn+` pointer must not be used again after link:libpq-connect.html#LIBPQ-PQFINISH[`+PQfinish+`] has been called.
[.term]#`+PQreset+` link:libpq-connect.html#LIBPQ-PQRESET[#]::
  Resets the communication channel to the server.
  +

  +
  This function will close the connection to the server and attempt to establish a new connection, using all the same parameters previously used. This might be useful for error recovery if a working connection is lost.
[.term]#`+PQresetStart+` +
#[.term]#`+PQresetPoll+` link:libpq-connect.html#LIBPQ-PQRESETSTART[#]::
  Reset the communication channel to the server, in a nonblocking manner.
  +

  +
  These functions will close the connection to the server and attempt to establish a new connection, using all the same parameters previously used. This can be useful for error recovery if a working connection is lost. They differ from link:libpq-connect.html#LIBPQ-PQRESET[`+PQreset+`] (above) in that they act in a nonblocking manner. These functions suffer from the same restrictions as link:libpq-connect.html#LIBPQ-PQCONNECTSTARTPARAMS[`+PQconnectStartParams+`], `+PQconnectStart+` and `+PQconnectPoll+`.
  +
  To initiate a connection reset, call link:libpq-connect.html#LIBPQ-PQRESETSTART[`+PQresetStart+`]. If it returns 0, the reset has failed. If it returns 1, poll the reset using `+PQresetPoll+` in exactly the same way as you would create the connection using `+PQconnectPoll+`.
[.term]#`+PQpingParams+` link:libpq-connect.html#LIBPQ-PQPINGPARAMS[#]::
  link:libpq-connect.html#LIBPQ-PQPINGPARAMS[`+PQpingParams+`] reports the status of the server. It accepts connection parameters identical to those of link:libpq-connect.html#LIBPQ-PQCONNECTDBPARAMS[`+PQconnectdbParams+`], described above. It is not necessary to supply correct user name, password, or database name values to obtain the server status; however, if incorrect values are provided, the server will log a failed connection attempt.
  +

  +
  The function returns one of the following values:
  +
  [.term]#`+PQPING_OK+`# link:libpq-connect.html#LIBPQ-PQPINGPARAMS-PQPING_OK[#];;
    The server is running and appears to be accepting connections.
  [.term]#`+PQPING_REJECT+`# link:libpq-connect.html#LIBPQ-PQPINGPARAMS-PQPING_REJECT[#];;
    The server is running but is in a state that disallows connections (startup, shutdown, or crash recovery).
  [.term]#`+PQPING_NO_RESPONSE+`# link:libpq-connect.html#LIBPQ-PQPINGPARAMS-PQPING_NO_RESPONSE[#];;
    The server could not be contacted. This might indicate that the server is not running, or that there is something wrong with the given connection parameters (for example, wrong port number), or that there is a network connectivity problem (for example, a firewall blocking the connection request).
  [.term]#`+PQPING_NO_ATTEMPT+`# link:libpq-connect.html#LIBPQ-PQPINGPARAMS-PQPING_NO_ATTEMPT[#];;
    No attempt was made to contact the server, because the supplied parameters were obviously incorrect or there was some client-side problem (for example, out of memory).
[.term]#`+PQping+` link:libpq-connect.html#LIBPQ-PQPING[#]::
  link:libpq-connect.html#LIBPQ-PQPING[`+PQping+`] reports the status of the server. It accepts connection parameters identical to those of link:libpq-connect.html#LIBPQ-PQCONNECTDB[`+PQconnectdb+`], described above. It is not necessary to supply correct user name, password, or database name values to obtain the server status; however, if incorrect values are provided, the server will log a failed connection attempt.
  +

  +
  The return values are the same as for link:libpq-connect.html#LIBPQ-PQPINGPARAMS[`+PQpingParams+`].
[.term]#`+PQsetSSLKeyPassHook_OpenSSL+` link:libpq-connect.html#LIBPQ-PQSETSSLKEYPASSHOOK-OPENSSL[#]::
  `+PQsetSSLKeyPassHook_OpenSSL+` lets an application override libpq's link:libpq-ssl.html#LIBPQ-SSL-CLIENTCERT[default handling of encrypted client certificate key files] using link:libpq-connect.html#LIBPQ-CONNECT-SSLPASSWORD[sslpassword] or interactive prompting.
  +

+
The application passes a pointer to a callback function with signature:
+

  +
  which libpq will then call [.emphasis]#_instead of_# its default `+PQdefaultSSLKeyPassHook_OpenSSL+` handler. The callback should determine the password for the key and copy it to result-buffer _`+buf+`_ of size _`+size+`_. The string in _`+buf+`_ must be null-terminated. The callback must return the length of the password stored in _`+buf+`_ excluding the null terminator. On failure, the callback should set `+buf[0] = '\0'+` and return 0. See `+PQdefaultSSLKeyPassHook_OpenSSL+` in libpq's source code for an example.
  +
  If the user specified an explicit key location, its path will be in `+conn->sslkey+` when the callback is invoked. This will be empty if the default key path is being used. For keys that are engine specifiers, it is up to engine implementations whether they use the OpenSSL password callback or define their own handling.
  +
  The app callback may choose to delegate unhandled cases to `+PQdefaultSSLKeyPassHook_OpenSSL+`, or call it first and try something else if it returns 0, or completely override it.
  +
  The callback [.emphasis]#_must not_# escape normal flow control with exceptions, `+longjmp(...)+`, etc. It must return normally.
[.term]#`+PQgetSSLKeyPassHook_OpenSSL+` link:libpq-connect.html#LIBPQ-PQGETSSLKEYPASSHOOK-OPENSSL[#]::
  `+PQgetSSLKeyPassHook_OpenSSL+` returns the current client certificate key password hook, or `+NULL+` if none has been set.
  +