PostgreSQL

33.4. Asynchronous Command Processing
Prev	Up	Chapter 33. libpq — C Library	Home	Next

33.4. Asynchronous Command Processing

The PQexec function is adequate for submitting commands in normal, synchronous applications. It has a few deficiencies, however, that can be of importance to some users:

PQexec waits for the command to be completed. The application might have other work to do (such as maintaining a user interface), in which case it won’t want to block waiting for the response.
Since the execution of the client application is suspended while it waits for the result, it is hard for the application to decide that it would like to try to cancel the ongoing command. (It can be done from a signal handler, but not otherwise.)
PQexec can return only one PGresult structure. If the submitted command string contains multiple SQL commands, all but the last PGresult are discarded by PQexec.
PQexec always collects the command’s entire result, buffering it in a single PGresult. While this simplifies error-handling logic for the application, it can be impractical for results containing many rows.

Applications that do not like these limitations can instead use the underlying functions that PQexec is built from: PQsendQuery and PQgetResult. There are also PQsendQueryParams, PQsendPrepare, PQsendQueryPrepared, PQsendDescribePrepared, and PQsendDescribePortal, which can be used with PQgetResult to duplicate the functionality of PQexecParams, PQprepare, PQexecPrepared, PQdescribePrepared, and PQdescribePortal respectively.

[.term]#PQsendQuery: Submits a command to the server without waiting for the result(s). 1 is returned if the command was successfully dispatched and 0 if not (in which case, use PQerrorMessage to get more information about the failure). +

int PQsendQuery(PGconn *conn, const char *command);

  +
  After successfully calling link:libpq-async.html#LIBPQ-PQSENDQUERY[`+PQsendQuery+`], call link:libpq-async.html#LIBPQ-PQGETRESULT[`+PQgetResult+`] one or more times to obtain the results. link:libpq-async.html#LIBPQ-PQSENDQUERY[`+PQsendQuery+`] cannot be called again (on the same connection) until link:libpq-async.html#LIBPQ-PQGETRESULT[`+PQgetResult+`] has returned a null pointer, indicating that the command is done.
[.term]#`+PQsendQueryParams+`::
  Submits a command and separate parameters to the server without waiting for the result(s).
  +

int PQsendQueryParams(PGconn *conn,
                      const char *command,
                      int nParams,
                      const Oid *paramTypes,
                      const char * const *paramValues,
                      const int *paramLengths,
                      const int *paramFormats,
                      int resultFormat);

  +
  This is equivalent to link:libpq-async.html#LIBPQ-PQSENDQUERY[`+PQsendQuery+`] except that query parameters can be specified separately from the query string. The function's parameters are handled identically to link:libpq-exec.html#LIBPQ-PQEXECPARAMS[`+PQexecParams+`]. Like link:libpq-exec.html#LIBPQ-PQEXECPARAMS[`+PQexecParams+`], it will not work on 2.0-protocol connections, and it allows only one command in the query string.
[.term]#`+PQsendPrepare+`::
  Sends a request to create a prepared statement with the given parameters, without waiting for completion.
  +

int PQsendPrepare(PGconn *conn,
                  const char *stmtName,
                  const char *query,
                  int nParams,
                  const Oid *paramTypes);

  +
  This is an asynchronous version of link:libpq-exec.html#LIBPQ-PQPREPARE[`+PQprepare+`]: it returns 1 if it was able to dispatch the request, and 0 if not. After a successful call, call link:libpq-async.html#LIBPQ-PQGETRESULT[`+PQgetResult+`] to determine whether the server successfully created the prepared statement. The function's parameters are handled identically to link:libpq-exec.html#LIBPQ-PQPREPARE[`+PQprepare+`]. Like link:libpq-exec.html#LIBPQ-PQPREPARE[`+PQprepare+`], it will not work on 2.0-protocol connections.
[.term]#`+PQsendQueryPrepared+`::
  Sends a request to execute a prepared statement with given parameters, without waiting for the result(s).
  +

int PQsendQueryPrepared(PGconn *conn,
                        const char *stmtName,
                        int nParams,
                        const char * const *paramValues,
                        const int *paramLengths,
                        const int *paramFormats,
                        int resultFormat);

  +
  This is similar to link:libpq-async.html#LIBPQ-PQSENDQUERYPARAMS[`+PQsendQueryParams+`], but the command to be executed is specified by naming a previously-prepared statement, instead of giving a query string. The function's parameters are handled identically to link:libpq-exec.html#LIBPQ-PQEXECPREPARED[`+PQexecPrepared+`]. Like link:libpq-exec.html#LIBPQ-PQEXECPREPARED[`+PQexecPrepared+`], it will not work on 2.0-protocol connections.
[.term]#`+PQsendDescribePrepared+`::
  Submits a request to obtain information about the specified prepared statement, without waiting for completion.
  +

int PQsendDescribePrepared(PGconn *conn, const char *stmtName);

  +
  This is an asynchronous version of link:libpq-exec.html#LIBPQ-PQDESCRIBEPREPARED[`+PQdescribePrepared+`]: it returns 1 if it was able to dispatch the request, and 0 if not. After a successful call, call link:libpq-async.html#LIBPQ-PQGETRESULT[`+PQgetResult+`] to obtain the results. The function's parameters are handled identically to link:libpq-exec.html#LIBPQ-PQDESCRIBEPREPARED[`+PQdescribePrepared+`]. Like link:libpq-exec.html#LIBPQ-PQDESCRIBEPREPARED[`+PQdescribePrepared+`], it will not work on 2.0-protocol connections.
[.term]#`+PQsendDescribePortal+`::
  Submits a request to obtain information about the specified portal, without waiting for completion.
  +

int PQsendDescribePortal(PGconn *conn, const char *portalName);

  +
  This is an asynchronous version of link:libpq-exec.html#LIBPQ-PQDESCRIBEPORTAL[`+PQdescribePortal+`]: it returns 1 if it was able to dispatch the request, and 0 if not. After a successful call, call link:libpq-async.html#LIBPQ-PQGETRESULT[`+PQgetResult+`] to obtain the results. The function's parameters are handled identically to link:libpq-exec.html#LIBPQ-PQDESCRIBEPORTAL[`+PQdescribePortal+`]. Like link:libpq-exec.html#LIBPQ-PQDESCRIBEPORTAL[`+PQdescribePortal+`], it will not work on 2.0-protocol connections.
[.term]#`+PQgetResult+`::
  Waits for the next result from a prior link:libpq-async.html#LIBPQ-PQSENDQUERY[`+PQsendQuery+`], link:libpq-async.html#LIBPQ-PQSENDQUERYPARAMS[`+PQsendQueryParams+`], link:libpq-async.html#LIBPQ-PQSENDPREPARE[`+PQsendPrepare+`], link:libpq-async.html#LIBPQ-PQSENDQUERYPREPARED[`+PQsendQueryPrepared+`], link:libpq-async.html#LIBPQ-PQSENDDESCRIBEPREPARED[`+PQsendDescribePrepared+`], or link:libpq-async.html#LIBPQ-PQSENDDESCRIBEPORTAL[`+PQsendDescribePortal+`] call, and returns it. A null pointer is returned when the command is complete and there will be no more results.
  +

PGresult *PQgetResult(PGconn *conn);

+
link:libpq-async.html#LIBPQ-PQGETRESULT[`+PQgetResult+`] must be called repeatedly until it returns a null pointer, indicating that the command is done. (If called when no command is active, link:libpq-async.html#LIBPQ-PQGETRESULT[`+PQgetResult+`] will just return a null pointer at once.) Each non-null result from link:libpq-async.html#LIBPQ-PQGETRESULT[`+PQgetResult+`] should be processed using the same `+PGresult+` accessor functions previously described. Don't forget to free each result object with link:libpq-exec.html#LIBPQ-PQCLEAR[`+PQclear+`] when done with it. Note that link:libpq-async.html#LIBPQ-PQGETRESULT[`+PQgetResult+`] will block only if a command is active and the necessary response data has not yet been read by link:libpq-async.html#LIBPQ-PQCONSUMEINPUT[`+PQconsumeInput+`] .
+
[NOTE]
====
==== Note

Even when link:libpq-exec.html#LIBPQ-PQRESULTSTATUS[`+PQresultStatus+`] indicates a fatal error, link:libpq-async.html#LIBPQ-PQGETRESULT[`+PQgetResult+`] should be called until it returns a null pointer, to allow libpq to process the error information completely.
====

Using PQsendQuery and PQgetResult solves one of PQexec's problems: If a command string contains multiple SQL commands, the results of those commands can be obtained individually. (This allows a simple form of overlapped processing, by the way: the client can be handling the results of one command while the server is still working on later queries in the same command string.)

Another frequently-desired feature that can be obtained with PQsendQuery and PQgetResult is retrieving large query results a row at a time. This is discussed in Section 33.5.

By itself, calling PQgetResult will still cause the client to block until the server completes the next SQL command. This can be avoided by proper use of two more functions:

[.term]#PQconsumeInput: If input is available from the server, consume it. +

int PQconsumeInput(PGconn *conn);

  +
  link:libpq-async.html#LIBPQ-PQCONSUMEINPUT[`+PQconsumeInput+`] normally returns 1 indicating [.quote]#“[.quote]#no error#”#, but returns 0 if there was some kind of trouble (in which case link:libpq-status.html#LIBPQ-PQERRORMESSAGE[`+PQerrorMessage+`] can be consulted). Note that the result does not say whether any input data was actually collected. After calling link:libpq-async.html#LIBPQ-PQCONSUMEINPUT[`+PQconsumeInput+`] , the application can check link:libpq-async.html#LIBPQ-PQISBUSY[`+PQisBusy+`] and/or `+PQnotifies+` to see if their state has changed.
  +
  link:libpq-async.html#LIBPQ-PQCONSUMEINPUT[`+PQconsumeInput+`] can be called even if the application is not prepared to deal with a result or notification just yet. The function will read available data and save it in a buffer, thereby causing a `+select()+` read-ready indication to go away. The application can thus use link:libpq-async.html#LIBPQ-PQCONSUMEINPUT[`+PQconsumeInput+`] to clear the `+select()+` condition immediately, and then examine the results at leisure.
[.term]#`+PQisBusy+`::
  Returns 1 if a command is busy, that is, link:libpq-async.html#LIBPQ-PQGETRESULT[`+PQgetResult+`] would block waiting for input. A 0 return indicates that link:libpq-async.html#LIBPQ-PQGETRESULT[`+PQgetResult+`] can be called with assurance of not blocking.
  +

int PQisBusy(PGconn *conn);

+
link:libpq-async.html#LIBPQ-PQISBUSY[`+PQisBusy+`] will not itself attempt to read data from the server; therefore link:libpq-async.html#LIBPQ-PQCONSUMEINPUT[`+PQconsumeInput+`] must be invoked first, or the busy state will never end.

A typical application using these functions will have a main loop that uses select() or poll() to wait for all the conditions that it must respond to. One of the conditions will be input available from the server, which in terms of select() means readable data on the file descriptor identified by PQsocket. When the main loop detects input ready, it should call PQconsumeInput to read the input. It can then call PQisBusy, followed by PQgetResult if PQisBusy returns false (0). It can also call PQnotifies to detect NOTIFY messages (see Section 33.8).

A client that uses PQsendQuery/PQgetResult can also attempt to cancel a command that is still being processed by the server; see Section 33.6. But regardless of the return value of PQcancel, the application must continue with the normal result-reading sequence using PQgetResult. A successful cancellation will simply cause the command to terminate sooner than it would have otherwise.

By using the functions described above, it is possible to avoid blocking while waiting for input from the database server. However, it is still possible that the application will block waiting to send output to the server. This is relatively uncommon but can happen if very long SQL commands or data values are sent. (It is much more probable if the application sends data via COPY IN, however.) To prevent this possibility and achieve completely nonblocking database operation, the following additional functions can be used.

[.term]#PQsetnonblocking: Sets the nonblocking status of the connection. +

int PQsetnonblocking(PGconn *conn, int arg);

  +
  Sets the state of the connection to nonblocking if _`+arg+`_ is 1, or blocking if _`+arg+`_ is 0. Returns 0 if OK, -1 if error.
  +
  In the nonblocking state, calls to link:libpq-async.html#LIBPQ-PQSENDQUERY[`+PQsendQuery+`], link:libpq-copy.html#LIBPQ-PQPUTLINE[`+PQputline+`], link:libpq-copy.html#LIBPQ-PQPUTNBYTES[`+PQputnbytes+`], link:libpq-copy.html#LIBPQ-PQPUTCOPYDATA[`+PQputCopyData+`], and link:libpq-copy.html#LIBPQ-PQENDCOPY[`+PQendcopy+`] will not block but instead return an error if they need to be called again.
  +
  Note that link:libpq-exec.html#LIBPQ-PQEXEC[`+PQexec+`] does not honor nonblocking mode; if it is called, it will act in blocking fashion anyway.
[.term]#`+PQisnonblocking+`::
  Returns the blocking status of the database connection.
  +

int PQisnonblocking(const PGconn *conn);

  +
  Returns 1 if the connection is set to nonblocking mode and 0 if blocking.
[.term]#`+PQflush+`::
  Attempts to flush any queued output data to the server. Returns 0 if successful (or if the send queue is empty), -1 if it failed for some reason, or 1 if it was unable to send all the data in the send queue yet (this case can only occur if the connection is nonblocking).
  +

int PQflush(PGconn *conn);

After sending any command or data on a nonblocking connection, call PQflush. If it returns 1, wait for the socket to become read- or write-ready. If it becomes write-ready, call PQflush again. If it becomes read-ready, call PQconsumeInput , then call PQflush again. Repeat until PQflush returns 0. (It is necessary to check for read-ready and drain the input with PQconsumeInput , because the server can block trying to send us data, e.g., NOTICE messages, and won’t read our data until we read its.) Once PQflush returns 0, wait for the socket to be read-ready and then read the response as described above.

Prev	Up	Next
33.3. Command Execution Functions	Home	33.5. Retrieving Query Results Row-by-Row

33.3. Command Execution Functions

Home

33.5. Retrieving Query Results Row-by-Row

Submit correction

If you see anything in the documentation that is not correct, does not match your experience with the particular feature or requires further clarification, please use this form to report a documentation issue.