PostgreSQL

+
Returns a `+PGresult+` pointer or possibly a null pointer. A non-null pointer will generally be returned except in out-of-memory conditions or serious errors such as inability to send the command to the server. The link:libpq-exec.html#LIBPQ-PQRESULTSTATUS[`+PQresultStatus+`] function should be called to check the return value for any errors (including the value of a null pointer, in which case it will return `+PGRES_FATAL_ERROR+`). Use link:libpq-status.html#LIBPQ-PQERRORMESSAGE[`+PQerrorMessage+`] to get more information about such errors.

+
link:libpq-exec.html#LIBPQ-PQEXECPARAMS[`+PQexecParams+`] is like link:libpq-exec.html#LIBPQ-PQEXEC[`+PQexec+`], but offers additional functionality: parameter values can be specified separately from the command string proper, and query results can be requested in either text or binary format.
+
The function arguments are:
+
[.term]#_`+conn+`_#;;
  The connection object to send the command through.
[.term]#_`+command+`_#;;
  The SQL command string to be executed. If parameters are used, they are referred to in the command string as `+$1+`, `+$2+`, etc.
[.term]#_`+nParams+`_#;;
  The number of parameters supplied; it is the length of the arrays _`+paramTypes[]+`_, _`+paramValues[]+`_, _`+paramLengths[]+`_, and _`+paramFormats[]+`_. (The array pointers can be `+NULL+` when _`+nParams+`_ is zero.)
[.term]#_`+paramTypes[]+`_#;;
  Specifies, by OID, the data types to be assigned to the parameter symbols. If _`+paramTypes+`_ is `+NULL+`, or any particular element in the array is zero, the server infers a data type for the parameter symbol in the same way it would do for an untyped literal string.
[.term]#_`+paramValues[]+`_#;;
  Specifies the actual values of the parameters. A null pointer in this array means the corresponding parameter is null; otherwise the pointer points to a zero-terminated text string (for text format) or binary data in the format expected by the server (for binary format).
[.term]#_`+paramLengths[]+`_#;;
  Specifies the actual data lengths of binary-format parameters. It is ignored for null parameters and text-format parameters. The array pointer can be null when there are no binary parameters.
[.term]#_`+paramFormats[]+`_#;;
  Specifies whether parameters are text (put a zero in the array entry for the corresponding parameter) or binary (put a one in the array entry for the corresponding parameter). If the array pointer is null then all parameters are presumed to be text strings.
  +
  Values passed in binary format require knowledge of the internal representation expected by the backend. For example, integers must be passed in network byte order. Passing `+numeric+` values requires knowledge of the server storage format, as implemented in `+src/backend/utils/adt/numeric.c::numeric_send()+` and `+src/backend/utils/adt/numeric.c::numeric_recv()+`.
[.term]#_`+resultFormat+`_#;;
  Specify zero to obtain results in text format, or one to obtain results in binary format. (There is not currently a provision to obtain different result columns in different formats, although that is possible in the underlying protocol.)

+
link:libpq-exec.html#LIBPQ-PQPREPARE[`+PQprepare+`] creates a prepared statement for later execution with link:libpq-exec.html#LIBPQ-PQEXECPREPARED[`+PQexecPrepared+`]. This feature allows commands to be executed repeatedly without being parsed and planned each time; see link:sql-prepare.html[[.refentrytitle]#PREPARE#] for details.
+
The function creates a prepared statement named _`+stmtName+`_ from the _`+query+`_ string, which must contain a single SQL command. _`+stmtName+`_ can be `+""+` to create an unnamed statement, in which case any pre-existing unnamed statement is automatically replaced; otherwise it is an error if the statement name is already defined in the current session. If any parameters are used, they are referred to in the query as `+$1+`, `+$2+`, etc. _`+nParams+`_ is the number of parameters for which types are pre-specified in the array _`+paramTypes[]+`_. (The array pointer can be `+NULL+` when _`+nParams+`_ is zero.) _`+paramTypes[]+`_ specifies, by OID, the data types to be assigned to the parameter symbols. If _`+paramTypes+`_ is `+NULL+`, or any particular element in the array is zero, the server assigns a data type to the parameter symbol in the same way it would do for an untyped literal string. Also, the query can use parameter symbols with numbers higher than _`+nParams+`_; data types will be inferred for these symbols as well. (See link:libpq-exec.html#LIBPQ-PQDESCRIBEPREPARED[`+PQdescribePrepared+`] for a means to find out what data types were inferred.)
+
As with link:libpq-exec.html#LIBPQ-PQEXEC[`+PQexec+`], the result is normally a `+PGresult+` object whose contents indicate server-side success or failure. A null result indicates out-of-memory or inability to send the command at all. Use link:libpq-status.html#LIBPQ-PQERRORMESSAGE[`+PQerrorMessage+`] to get more information about such errors.

  +
  link:libpq-exec.html#LIBPQ-PQEXECPREPARED[`+PQexecPrepared+`] is like link:libpq-exec.html#LIBPQ-PQEXECPARAMS[`+PQexecParams+`], but the command to be executed is specified by naming a previously-prepared statement, instead of giving a query string. This feature allows commands that will be used repeatedly to be parsed and planned just once, rather than each time they are executed. The statement must have been prepared previously in the current session.
  +
  The parameters are identical to link:libpq-exec.html#LIBPQ-PQEXECPARAMS[`+PQexecParams+`], except that the name of a prepared statement is given instead of a query string, and the _`+paramTypes[]+`_ parameter is not present (it is not needed since the prepared statement's parameter types were determined when it was created).
[.term]#`+PQdescribePrepared+` link:libpq-exec.html#LIBPQ-PQDESCRIBEPREPARED[#]::
  Submits a request to obtain information about the specified prepared statement, and waits for completion.
  +

  +
  link:libpq-exec.html#LIBPQ-PQDESCRIBEPREPARED[`+PQdescribePrepared+`] allows an application to obtain information about a previously prepared statement.
  +
  _`+stmtName+`_ can be `+""+` or `+NULL+` to reference the unnamed statement, otherwise it must be the name of an existing prepared statement. On success, a `+PGresult+` with status `+PGRES_COMMAND_OK+` is returned. The functions link:libpq-exec.html#LIBPQ-PQNPARAMS[`+PQnparams+`] and link:libpq-exec.html#LIBPQ-PQPARAMTYPE[`+PQparamtype+`] can be applied to this `+PGresult+` to obtain information about the parameters of the prepared statement, and the functions link:libpq-exec.html#LIBPQ-PQNFIELDS[`+PQnfields+`], link:libpq-exec.html#LIBPQ-PQFNAME[`+PQfname+`], link:libpq-exec.html#LIBPQ-PQFTYPE[`+PQftype+`], etc. provide information about the result columns (if any) of the statement.
[.term]#`+PQdescribePortal+` link:libpq-exec.html#LIBPQ-PQDESCRIBEPORTAL[#]::
  Submits a request to obtain information about the specified portal, and waits for completion.
  +

+
link:libpq-exec.html#LIBPQ-PQDESCRIBEPORTAL[`+PQdescribePortal+`] allows an application to obtain information about a previously created portal. (libpq does not provide any direct access to portals, but you can use this function to inspect the properties of a cursor created with a `+DECLARE CURSOR+` SQL command.)
+
_`+portalName+`_ can be `+""+` or `+NULL+` to reference the unnamed portal, otherwise it must be the name of an existing portal. On success, a `+PGresult+` with status `+PGRES_COMMAND_OK+` is returned. The functions link:libpq-exec.html#LIBPQ-PQNFIELDS[`+PQnfields+`], link:libpq-exec.html#LIBPQ-PQFNAME[`+PQfname+`], link:libpq-exec.html#LIBPQ-PQFTYPE[`+PQftype+`], etc. can be applied to the `+PGresult+` to obtain information about the result columns (if any) of the portal.

  +
  link:libpq-exec.html#LIBPQ-PQRESULTSTATUS[`+PQresultStatus+`] can return one of the following values:
  +
  [.term]#`+PGRES_EMPTY_QUERY+`# link:libpq-exec.html#LIBPQ-PGRES-EMPTY-QUERY[#];;
    The string sent to the server was empty.
  [.term]#`+PGRES_COMMAND_OK+`# link:libpq-exec.html#LIBPQ-PGRES-COMMAND-OK[#];;
    Successful completion of a command returning no data.
  [.term]#`+PGRES_TUPLES_OK+`# link:libpq-exec.html#LIBPQ-PGRES-TUPLES-OK[#];;
    Successful completion of a command returning data (such as a `+SELECT+` or `+SHOW+`).
  [.term]#`+PGRES_COPY_OUT+`# link:libpq-exec.html#LIBPQ-PGRES-COPY-OUT[#];;
    Copy Out (from server) data transfer started.
  [.term]#`+PGRES_COPY_IN+`# link:libpq-exec.html#LIBPQ-PGRES-COPY-IN[#];;
    Copy In (to server) data transfer started.
  [.term]#`+PGRES_BAD_RESPONSE+`# link:libpq-exec.html#LIBPQ-PGRES-BAD-RESPONSE[#];;
    The server's response was not understood.
  [.term]#`+PGRES_NONFATAL_ERROR+`# link:libpq-exec.html#LIBPQ-PGRES-NONFATAL-ERROR[#];;
    A nonfatal error (a notice or warning) occurred.
  [.term]#`+PGRES_FATAL_ERROR+`# link:libpq-exec.html#LIBPQ-PGRES-FATAL-ERROR[#];;
    A fatal error occurred.
  [.term]#`+PGRES_COPY_BOTH+`# link:libpq-exec.html#LIBPQ-PGRES-COPY-BOTH[#];;
    Copy In/Out (to and from server) data transfer started. This feature is currently used only for streaming replication, so this status should not occur in ordinary applications.
  [.term]#`+PGRES_SINGLE_TUPLE+`# link:libpq-exec.html#LIBPQ-PGRES-SINGLE-TUPLE[#];;
    The `+PGresult+` contains a single result tuple from the current command. This status occurs only when single-row mode has been selected for the query (see link:libpq-single-row-mode.html[Section 34.6]).
  [.term]#`+PGRES_PIPELINE_SYNC+`# link:libpq-exec.html#LIBPQ-PGRES-PIPELINE-SYNC[#];;
    The `+PGresult+` represents a synchronization point in pipeline mode, requested by link:libpq-pipeline-mode.html#LIBPQ-PQPIPELINESYNC[`+PQpipelineSync+`]. This status occurs only when pipeline mode has been selected.
  [.term]#`+PGRES_PIPELINE_ABORTED+`# link:libpq-exec.html#LIBPQ-PGRES-PIPELINE-ABORTED[#];;
    The `+PGresult+` represents a pipeline that has received an error from the server. `+PQgetResult+` must be called repeatedly, and each time it will return this status code until the end of the current pipeline, at which point it will return `+PGRES_PIPELINE_SYNC+` and normal processing can resume.
  +
  If the result status is `+PGRES_TUPLES_OK+` or `+PGRES_SINGLE_TUPLE+`, then the functions described below can be used to retrieve the rows returned by the query. Note that a `+SELECT+` command that happens to retrieve zero rows still shows `+PGRES_TUPLES_OK+`. `+PGRES_COMMAND_OK+` is for commands that can never return rows (`+INSERT+` or `+UPDATE+` without a `+RETURNING+` clause, etc.). A response of `+PGRES_EMPTY_QUERY+` might indicate a bug in the client software.
  +
  A result of status `+PGRES_NONFATAL_ERROR+` will never be returned directly by link:libpq-exec.html#LIBPQ-PQEXEC[`+PQexec+`] or other query execution functions; results of this kind are instead passed to the notice processor (see link:libpq-notice-processing.html[Section 34.13]).
[.term]#`+PQresStatus+` link:libpq-exec.html#LIBPQ-PQRESSTATUS[#]::
  Converts the enumerated type returned by link:libpq-exec.html#LIBPQ-PQRESULTSTATUS[`+PQresultStatus+`] into a string constant describing the status code. The caller should not free the result.
  +

  +
  If there was an error, the returned string will include a trailing newline. The caller should not free the result directly. It will be freed when the associated `+PGresult+` handle is passed to link:libpq-exec.html#LIBPQ-PQCLEAR[`+PQclear+`].
  +
  Immediately following a link:libpq-exec.html#LIBPQ-PQEXEC[`+PQexec+`] or link:libpq-async.html#LIBPQ-PQGETRESULT[`+PQgetResult+`] call, link:libpq-status.html#LIBPQ-PQERRORMESSAGE[`+PQerrorMessage+`] (on the connection) will return the same string as link:libpq-exec.html#LIBPQ-PQRESULTERRORMESSAGE[`+PQresultErrorMessage+`] (on the result). However, a `+PGresult+` will retain its error message until destroyed, whereas the connection's error message will change when subsequent operations are done. Use link:libpq-exec.html#LIBPQ-PQRESULTERRORMESSAGE[`+PQresultErrorMessage+`] when you want to know the status associated with a particular `+PGresult+`; use link:libpq-status.html#LIBPQ-PQERRORMESSAGE[`+PQerrorMessage+`] when you want to know the status from the latest operation on the connection.
[.term]#`+PQresultVerboseErrorMessage+` link:libpq-exec.html#LIBPQ-PQRESULTVERBOSEERRORMESSAGE[#]::
  Returns a reformatted version of the error message associated with a `+PGresult+` object.
  +

  +
  In some situations a client might wish to obtain a more detailed version of a previously-reported error. link:libpq-exec.html#LIBPQ-PQRESULTVERBOSEERRORMESSAGE[`+PQresultVerboseErrorMessage+`] addresses this need by computing the message that would have been produced by link:libpq-exec.html#LIBPQ-PQRESULTERRORMESSAGE[`+PQresultErrorMessage+`] if the specified verbosity settings had been in effect for the connection when the given `+PGresult+` was generated. If the `+PGresult+` is not an error result, [.quote]#“[.quote]#PGresult is not an error result#”# is reported instead. The returned string includes a trailing newline.
  +
  Unlike most other functions for extracting data from a `+PGresult+`, the result of this function is a freshly allocated string. The caller must free it using `+PQfreemem()+` when the string is no longer needed.
  +
  A NULL return is possible if there is insufficient memory.
[.term]#`+PQresultErrorField+` link:libpq-exec.html#LIBPQ-PQRESULTERRORFIELD[#]::
  Returns an individual field of an error report.
  +

+
_`+fieldcode+`_ is an error field identifier; see the symbols listed below. `+NULL+` is returned if the `+PGresult+` is not an error or warning result, or does not include the specified field. Field values will normally not include a trailing newline. The caller should not free the result directly. It will be freed when the associated `+PGresult+` handle is passed to link:libpq-exec.html#LIBPQ-PQCLEAR[`+PQclear+`].
+
The following field codes are available:
+
[.term]#`+PG_DIAG_SEVERITY+`# link:libpq-exec.html#LIBPQ-PG-DIAG-SEVERITY[#];;
  The severity; the field contents are `+ERROR+`, `+FATAL+`, or `+PANIC+` (in an error message), or `+WARNING+`, `+NOTICE+`, `+DEBUG+`, `+INFO+`, or `+LOG+` (in a notice message), or a localized translation of one of these. Always present.
[.term]#`+PG_DIAG_SEVERITY_NONLOCALIZED+`# link:libpq-exec.html#LIBPQ-PG-DIAG-SEVERITY-NONLOCALIZED[#];;
  The severity; the field contents are `+ERROR+`, `+FATAL+`, or `+PANIC+` (in an error message), or `+WARNING+`, `+NOTICE+`, `+DEBUG+`, `+INFO+`, or `+LOG+` (in a notice message). This is identical to the `+PG_DIAG_SEVERITY+` field except that the contents are never localized. This is present only in reports generated by PostgreSQL versions 9.6 and later.
[.term]#`+PG_DIAG_SQLSTATE+` link:libpq-exec.html#LIBPQ-PG-DIAG-SQLSTATE[#];;
  The SQLSTATE code for the error. The SQLSTATE code identifies the type of error that has occurred; it can be used by front-end applications to perform specific operations (such as error handling) in response to a particular database error. For a list of the possible SQLSTATE codes, see link:errcodes-appendix.html[Appendix A]. This field is not localizable, and is always present.
[.term]#`+PG_DIAG_MESSAGE_PRIMARY+`# link:libpq-exec.html#LIBPQ-PG-DIAG-MESSAGE-PRIMARY[#];;
  The primary human-readable error message (typically one line). Always present.
[.term]#`+PG_DIAG_MESSAGE_DETAIL+`# link:libpq-exec.html#LIBPQ-PG-DIAG-MESSAGE-DETAIL[#];;
  Detail: an optional secondary error message carrying more detail about the problem. Might run to multiple lines.
[.term]#`+PG_DIAG_MESSAGE_HINT+`# link:libpq-exec.html#LIBPQ-PG-DIAG-MESSAGE-HINT[#];;
  Hint: an optional suggestion what to do about the problem. This is intended to differ from detail in that it offers advice (potentially inappropriate) rather than hard facts. Might run to multiple lines.
[.term]#`+PG_DIAG_STATEMENT_POSITION+`# link:libpq-exec.html#LIBPQ-PG-DIAG-STATEMENT-POSITION[#];;
  A string containing a decimal integer indicating an error cursor position as an index into the original statement string. The first character has index 1, and positions are measured in characters not bytes.
[.term]#`+PG_DIAG_INTERNAL_POSITION+`# link:libpq-exec.html#LIBPQ-PG-DIAG-INTERNAL-POSITION[#];;
  This is defined the same as the `+PG_DIAG_STATEMENT_POSITION+` field, but it is used when the cursor position refers to an internally generated command rather than the one submitted by the client. The `+PG_DIAG_INTERNAL_QUERY+` field will always appear when this field appears.
[.term]#`+PG_DIAG_INTERNAL_QUERY+`# link:libpq-exec.html#LIBPQ-PG-DIAG-INTERNAL-QUERY[#];;
  The text of a failed internally-generated command. This could be, for example, an SQL query issued by a PL/pgSQL function.
[.term]#`+PG_DIAG_CONTEXT+`# link:libpq-exec.html#LIBPQ-PG-DIAG-CONTEXT[#];;
  An indication of the context in which the error occurred. Presently this includes a call stack traceback of active procedural language functions and internally-generated queries. The trace is one entry per line, most recent first.
[.term]#`+PG_DIAG_SCHEMA_NAME+`# link:libpq-exec.html#LIBPQ-PG-DIAG-SCHEMA-NAME[#];;
  If the error was associated with a specific database object, the name of the schema containing that object, if any.
[.term]#`+PG_DIAG_TABLE_NAME+`# link:libpq-exec.html#LIBPQ-PG-DIAG-TABLE-NAME[#];;
  If the error was associated with a specific table, the name of the table. (Refer to the schema name field for the name of the table's schema.)
[.term]#`+PG_DIAG_COLUMN_NAME+`# link:libpq-exec.html#LIBPQ-PG-DIAG-COLUMN-NAME[#];;
  If the error was associated with a specific table column, the name of the column. (Refer to the schema and table name fields to identify the table.)
[.term]#`+PG_DIAG_DATATYPE_NAME+`# link:libpq-exec.html#LIBPQ-PG-DIAG-DATATYPE-NAME[#];;
  If the error was associated with a specific data type, the name of the data type. (Refer to the schema name field for the name of the data type's schema.)
[.term]#`+PG_DIAG_CONSTRAINT_NAME+`# link:libpq-exec.html#LIBPQ-PG-DIAG-CONSTRAINT-NAME[#];;
  If the error was associated with a specific constraint, the name of the constraint. Refer to fields listed above for the associated table or domain. (For this purpose, indexes are treated as constraints, even if they weren't created with constraint syntax.)
[.term]#`+PG_DIAG_SOURCE_FILE+`# link:libpq-exec.html#LIBPQ-PG-DIAG-SOURCE-FILE[#];;
  The file name of the source-code location where the error was reported.
[.term]#`+PG_DIAG_SOURCE_LINE+`# link:libpq-exec.html#LIBPQ-PG-DIAG-SOURCE-LINE[#];;
  The line number of the source-code location where the error was reported.
[.term]#`+PG_DIAG_SOURCE_FUNCTION+`# link:libpq-exec.html#LIBPQ-PG-DIAG-SOURCE-FUNCTION[#];;
  The name of the source-code function reporting the error.
+
[NOTE]
====
==== Note

  The fields for schema name, table name, column name, data type name, and constraint name are supplied only for a limited number of error types; see link:errcodes-appendix.html[Appendix A]. Do not assume that the presence of any of these fields guarantees the presence of another field. Core error sources observe the interrelationships noted above, but user-defined functions may use these fields in other ways. In the same vein, do not assume that these fields denote contemporary objects in the current database.
  ====
  +
  The client is responsible for formatting displayed information to meet its needs; in particular it should break long lines as needed. Newline characters appearing in the error message fields should be treated as paragraph breaks, not line breaks.
  +
  Errors generated internally by libpq will have severity and primary message, but typically no other fields.
  +
  Note that error fields are only available from `+PGresult+` objects, not `+PGconn+` objects; there is no `+PQerrorField+` function.
[.term]#`+PQclear+` link:libpq-exec.html#LIBPQ-PQCLEAR[#]::
  Frees the storage associated with a `+PGresult+`. Every command result should be freed via link:libpq-exec.html#LIBPQ-PQCLEAR[`+PQclear+`] when it is no longer needed.
  +

+
If the argument is a `+NULL+` pointer, no operation is performed.
+
You can keep a `+PGresult+` object around for as long as you need it; it does not go away when you issue a new command, nor even if you close the connection. To get rid of it, you must call link:libpq-exec.html#LIBPQ-PQCLEAR[`+PQclear+`]. Failure to do this will result in memory leaks in your application.

  +
  `+NULL+` is returned if the column number is out of range.
[.term]#`+PQfnumber+` link:libpq-exec.html#LIBPQ-PQFNUMBER[#]::
  Returns the column number associated with the given column name.
  +

+
-1 is returned if the given name does not match any column.
+
The given name is treated like an identifier in an SQL command, that is, it is downcased unless double-quoted. For example, given a query result generated from the SQL command:
+

+
we would have the results:
+

  +
  `+InvalidOid+` is returned if the column number is out of range, or if the specified column is not a simple reference to a table column. You can query the system table `+pg_class+` to determine exactly which table is referenced.
  +
  The type `+Oid+` and the constant `+InvalidOid+` will be defined when you include the libpq header file. They will both be some integer type.
[.term]#`+PQftablecol+` link:libpq-exec.html#LIBPQ-PQFTABLECOL[#]::
  Returns the column number (within its table) of the column making up the specified query result column. Query-result column numbers start at 0, but table columns have nonzero numbers.
  +

  +
  Zero is returned if the column number is out of range, or if the specified column is not a simple reference to a table column.
[.term]#`+PQfformat+` link:libpq-exec.html#LIBPQ-PQFFORMAT[#]::
  Returns the format code indicating the format of the given column. Column numbers start at 0.
  +

  +
  Format code zero indicates textual data representation, while format code one indicates binary representation. (Other codes are reserved for future definition.)
[.term]#`+PQftype+` link:libpq-exec.html#LIBPQ-PQFTYPE[#]::
  Returns the data type associated with the given column number. The integer returned is the internal OID number of the type. Column numbers start at 0.
  +

  +
  You can query the system table `+pg_type+` to obtain the names and properties of the various data types. The OIDs of the built-in data types are defined in the file `+catalog/pg_type_d.h+` in the PostgreSQL installation's `+include+` directory.
[.term]#`+PQfmod+` link:libpq-exec.html#LIBPQ-PQFMOD[#]::
  Returns the type modifier of the column associated with the given column number. Column numbers start at 0.
  +

  +
  The interpretation of modifier values is type-specific; they typically indicate precision or size limits. The value -1 is used to indicate [.quote]#“[.quote]#no information available#”#. Most data types do not use modifiers, in which case the value is always -1.
[.term]#`+PQfsize+` link:libpq-exec.html#LIBPQ-PQFSIZE[#]::
  Returns the size in bytes of the column associated with the given column number. Column numbers start at 0.
  +

  +
  link:libpq-exec.html#LIBPQ-PQFSIZE[`+PQfsize+`] returns the space allocated for this column in a database row, in other words the size of the server's internal representation of the data type. (Accordingly, it is not really very useful to clients.) A negative value indicates the data type is variable-length.
[.term]#`+PQbinaryTuples+` link:libpq-exec.html#LIBPQ-PQBINARYTUPLES[#]::
  Returns 1 if the `+PGresult+` contains binary data and 0 if it contains text data.
  +

  +
  This function is deprecated (except for its use in connection with `+COPY+`), because it is possible for a single `+PGresult+` to contain text data in some columns and binary data in others. link:libpq-exec.html#LIBPQ-PQFFORMAT[`+PQfformat+`] is preferred. link:libpq-exec.html#LIBPQ-PQBINARYTUPLES[`+PQbinaryTuples+`] returns 1 only if all columns of the result are binary (format 1).
[.term]#`+PQgetvalue+` link:libpq-exec.html#LIBPQ-PQGETVALUE[#]::
  Returns a single field value of one row of a `+PGresult+`. Row and column numbers start at 0. The caller should not free the result directly. It will be freed when the associated `+PGresult+` handle is passed to link:libpq-exec.html#LIBPQ-PQCLEAR[`+PQclear+`].
  +

  +
  For data in text format, the value returned by link:libpq-exec.html#LIBPQ-PQGETVALUE[`+PQgetvalue+`] is a null-terminated character string representation of the field value. For data in binary format, the value is in the binary representation determined by the data type's `+typsend+` and `+typreceive+` functions. (The value is actually followed by a zero byte in this case too, but that is not ordinarily useful, since the value is likely to contain embedded nulls.)
  +
  An empty string is returned if the field value is null. See link:libpq-exec.html#LIBPQ-PQGETISNULL[`+PQgetisnull+`] to distinguish null values from empty-string values.
  +
  The pointer returned by link:libpq-exec.html#LIBPQ-PQGETVALUE[`+PQgetvalue+`] points to storage that is part of the `+PGresult+` structure. One should not modify the data it points to, and one must explicitly copy the data into other storage if it is to be used past the lifetime of the `+PGresult+` structure itself.
[.term]#`+PQgetisnull+` link:libpq-exec.html#LIBPQ-PQGETISNULL[#]::
  Tests a field for a null value. Row and column numbers start at 0.
  +

  +
  This function returns 1 if the field is null and 0 if it contains a non-null value. (Note that link:libpq-exec.html#LIBPQ-PQGETVALUE[`+PQgetvalue+`] will return an empty string, not a null pointer, for a null field.)
[.term]#`+PQgetlength+` link:libpq-exec.html#LIBPQ-PQGETLENGTH[#]::
  Returns the actual length of a field value in bytes. Row and column numbers start at 0.
  +

  +
  This is the actual data length for the particular data value, that is, the size of the object pointed to by link:libpq-exec.html#LIBPQ-PQGETVALUE[`+PQgetvalue+`]. For text data format this is the same as `+strlen()+`. For binary format this is essential information. Note that one should [.emphasis]#_not_# rely on link:libpq-exec.html#LIBPQ-PQFSIZE[`+PQfsize+`] to obtain the actual data length.
[.term]#`+PQnparams+` link:libpq-exec.html#LIBPQ-PQNPARAMS[#]::
  Returns the number of parameters of a prepared statement.
  +

  +
  This function is only useful when inspecting the result of link:libpq-exec.html#LIBPQ-PQDESCRIBEPREPARED[`+PQdescribePrepared+`]. For other types of results it will return zero.
[.term]#`+PQparamtype+` link:libpq-exec.html#LIBPQ-PQPARAMTYPE[#]::
  Returns the data type of the indicated statement parameter. Parameter numbers start at 0.
  +

  +
  This function is only useful when inspecting the result of link:libpq-exec.html#LIBPQ-PQDESCRIBEPREPARED[`+PQdescribePrepared+`]. For other types of results it will return zero.
[.term]#`+PQprint+` link:libpq-exec.html#LIBPQ-PQPRINT[#]::
  Prints out all the rows and, optionally, the column names to the specified output stream.
  +

+
This function was formerly used by psql to print query results, but this is no longer the case. Note that it assumes all the data is in text format.

  +
  Commonly this is just the name of the command, but it might include additional data such as the number of rows processed. The caller should not free the result directly. It will be freed when the associated `+PGresult+` handle is passed to link:libpq-exec.html#LIBPQ-PQCLEAR[`+PQclear+`].
[.term]#`+PQcmdTuples+` link:libpq-exec.html#LIBPQ-PQCMDTUPLES[#]::
  Returns the number of rows affected by the SQL command.
  +

  +
  This function returns a string containing the number of rows affected by the SQL statement that generated the `+PGresult+`. This function can only be used following the execution of a `+SELECT+`, `+CREATE TABLE AS+`, `+INSERT+`, `+UPDATE+`, `+DELETE+`, `+MERGE+`, `+MOVE+`, `+FETCH+`, or `+COPY+` statement, or an `+EXECUTE+` of a prepared query that contains an `+INSERT+`, `+UPDATE+`, `+DELETE+`, or `+MERGE+` statement. If the command that generated the `+PGresult+` was anything else, link:libpq-exec.html#LIBPQ-PQCMDTUPLES[`+PQcmdTuples+`] returns an empty string. The caller should not free the return value directly. It will be freed when the associated `+PGresult+` handle is passed to link:libpq-exec.html#LIBPQ-PQCLEAR[`+PQclear+`].
[.term]#`+PQoidValue+` link:libpq-exec.html#LIBPQ-PQOIDVALUE[#]::
  Returns the OID of the inserted row, if the SQL command was an `+INSERT+` that inserted exactly one row into a table that has OIDs, or a `+EXECUTE+` of a prepared query containing a suitable `+INSERT+` statement. Otherwise, this function returns `+InvalidOid+`. This function will also return `+InvalidOid+` if the table affected by the `+INSERT+` statement does not contain OIDs.
  +

+
link:libpq-exec.html#LIBPQ-PQESCAPELITERAL[`+PQescapeLiteral+`] escapes a string for use within an SQL command. This is useful when inserting data values as literal constants in SQL commands. Certain characters (such as quotes and backslashes) must be escaped to prevent them from being interpreted specially by the SQL parser. link:libpq-exec.html#LIBPQ-PQESCAPELITERAL[`+PQescapeLiteral+`] performs this operation.
+
link:libpq-exec.html#LIBPQ-PQESCAPELITERAL[`+PQescapeLiteral+`] returns an escaped version of the _`+str+`_ parameter in memory allocated with `+malloc()+`. This memory should be freed using `+PQfreemem()+` when the result is no longer needed. A terminating zero byte is not required, and should not be counted in _`+length+`_. (If a terminating zero byte is found before _`+length+`_ bytes are processed, link:libpq-exec.html#LIBPQ-PQESCAPELITERAL[`+PQescapeLiteral+`] stops at the zero; the behavior is thus rather like `+strncpy+`.) The return string has all special characters replaced so that they can be properly processed by the PostgreSQL string literal parser. A terminating zero byte is also added. The single quotes that must surround PostgreSQL string literals are included in the result string.
+
On error, link:libpq-exec.html#LIBPQ-PQESCAPELITERAL[`+PQescapeLiteral+`] returns `+NULL+` and a suitable message is stored in the _`+conn+`_ object.
+
[TIP]
====
==== Tip

  It is especially important to do proper escaping when handling strings that were received from an untrustworthy source. Otherwise there is a security risk: you are vulnerable to [.quote]#“[.quote]#SQL injection#”# attacks wherein unwanted SQL commands are fed to your database.
  ====
  +
  Note that it is neither necessary nor correct to do escaping when a data value is passed as a separate parameter in link:libpq-exec.html#LIBPQ-PQEXECPARAMS[`+PQexecParams+`] or its sibling routines.
[.term]#`+PQescapeIdentifier+` link:libpq-exec.html#LIBPQ-PQESCAPEIDENTIFIER[#]::

+
link:libpq-exec.html#LIBPQ-PQESCAPEIDENTIFIER[`+PQescapeIdentifier+`] escapes a string for use as an SQL identifier, such as a table, column, or function name. This is useful when a user-supplied identifier might contain special characters that would otherwise not be interpreted as part of the identifier by the SQL parser, or when the identifier might contain upper case characters whose case should be preserved.
+
link:libpq-exec.html#LIBPQ-PQESCAPEIDENTIFIER[`+PQescapeIdentifier+`] returns a version of the _`+str+`_ parameter escaped as an SQL identifier in memory allocated with `+malloc()+`. This memory must be freed using `+PQfreemem()+` when the result is no longer needed. A terminating zero byte is not required, and should not be counted in _`+length+`_. (If a terminating zero byte is found before _`+length+`_ bytes are processed, link:libpq-exec.html#LIBPQ-PQESCAPEIDENTIFIER[`+PQescapeIdentifier+`] stops at the zero; the behavior is thus rather like `+strncpy+`.) The return string has all special characters replaced so that it will be properly processed as an SQL identifier. A terminating zero byte is also added. The return string will also be surrounded by double quotes.
+
On error, link:libpq-exec.html#LIBPQ-PQESCAPEIDENTIFIER[`+PQescapeIdentifier+`] returns `+NULL+` and a suitable message is stored in the _`+conn+`_ object.
+
[TIP]
====
==== Tip

  As with string literals, to prevent SQL injection attacks, SQL identifiers must be escaped when they are received from an untrustworthy source.
  ====
[.term]#`+PQescapeStringConn+` link:libpq-exec.html#LIBPQ-PQESCAPESTRINGCONN[#]::

  +
  link:libpq-exec.html#LIBPQ-PQESCAPESTRINGCONN[`+PQescapeStringConn+`] escapes string literals, much like link:libpq-exec.html#LIBPQ-PQESCAPELITERAL[`+PQescapeLiteral+`]. Unlike link:libpq-exec.html#LIBPQ-PQESCAPELITERAL[`+PQescapeLiteral+`], the caller is responsible for providing an appropriately sized buffer. Furthermore, link:libpq-exec.html#LIBPQ-PQESCAPESTRINGCONN[`+PQescapeStringConn+`] does not generate the single quotes that must surround PostgreSQL string literals; they should be provided in the SQL command that the result is inserted into. The parameter _`+from+`_ points to the first character of the string that is to be escaped, and the _`+length+`_ parameter gives the number of bytes in this string. A terminating zero byte is not required, and should not be counted in _`+length+`_. (If a terminating zero byte is found before _`+length+`_ bytes are processed, link:libpq-exec.html#LIBPQ-PQESCAPESTRINGCONN[`+PQescapeStringConn+`] stops at the zero; the behavior is thus rather like `+strncpy+`.) _`+to+`_ shall point to a buffer that is able to hold at least one more byte than twice the value of _`+length+`_, otherwise the behavior is undefined. Behavior is likewise undefined if the _`+to+`_ and _`+from+`_ strings overlap.
  +
  If the _`+error+`_ parameter is not `+NULL+`, then `+*error+` is set to zero on success, nonzero on error. Presently the only possible error conditions involve invalid multibyte encoding in the source string. The output string is still generated on error, but it can be expected that the server will reject it as malformed. On error, a suitable message is stored in the _`+conn+`_ object, whether or not _`+error+`_ is `+NULL+`.
  +
  link:libpq-exec.html#LIBPQ-PQESCAPESTRINGCONN[`+PQescapeStringConn+`] returns the number of bytes written to _`+to+`_, not including the terminating zero byte.
[.term]#`+PQescapeString+` link:libpq-exec.html#LIBPQ-PQESCAPESTRING[#]::
  link:libpq-exec.html#LIBPQ-PQESCAPESTRING[`+PQescapeString+`] is an older, deprecated version of link:libpq-exec.html#LIBPQ-PQESCAPESTRINGCONN[`+PQescapeStringConn+`].
  +

  +
  The only difference from link:libpq-exec.html#LIBPQ-PQESCAPESTRINGCONN[`+PQescapeStringConn+`] is that link:libpq-exec.html#LIBPQ-PQESCAPESTRING[`+PQescapeString+`] does not take `+PGconn+` or _`+error+`_ parameters. Because of this, it cannot adjust its behavior depending on the connection properties (such as character encoding) and therefore [.emphasis]#_it might give the wrong results_#. Also, it has no way to report error conditions.
  +
  link:libpq-exec.html#LIBPQ-PQESCAPESTRING[`+PQescapeString+`] can be used safely in client programs that work with only one PostgreSQL connection at a time (in this case it can find out what it needs to know [.quote]#“[.quote]#behind the scenes#”#). In other contexts it is a security hazard and should be avoided in favor of link:libpq-exec.html#LIBPQ-PQESCAPESTRINGCONN[`+PQescapeStringConn+`].
[.term]#`+PQescapeByteaConn+` link:libpq-exec.html#LIBPQ-PQESCAPEBYTEACONN[#]::
  Escapes binary data for use within an SQL command with the type `+bytea+`. As with link:libpq-exec.html#LIBPQ-PQESCAPESTRINGCONN[`+PQescapeStringConn+`], this is only used when inserting data directly into an SQL command string.
  +

  +
  Certain byte values must be escaped when used as part of a `+bytea+` literal in an SQL statement. link:libpq-exec.html#LIBPQ-PQESCAPEBYTEACONN[`+PQescapeByteaConn+`] escapes bytes using either hex encoding or backslash escaping. See link:datatype-binary.html[Section 8.4] for more information.
  +
  The _`+from+`_ parameter points to the first byte of the string that is to be escaped, and the _`+from_length+`_ parameter gives the number of bytes in this binary string. (A terminating zero byte is neither necessary nor counted.) The _`+to_length+`_ parameter points to a variable that will hold the resultant escaped string length. This result string length includes the terminating zero byte of the result.
  +
  link:libpq-exec.html#LIBPQ-PQESCAPEBYTEACONN[`+PQescapeByteaConn+`] returns an escaped version of the _`+from+`_ parameter binary string in memory allocated with `+malloc()+`. This memory should be freed using `+PQfreemem()+` when the result is no longer needed. The return string has all special characters replaced so that they can be properly processed by the PostgreSQL string literal parser, and the `+bytea+` input function. A terminating zero byte is also added. The single quotes that must surround PostgreSQL string literals are not part of the result string.
  +
  On error, a null pointer is returned, and a suitable error message is stored in the _`+conn+`_ object. Currently, the only possible error is insufficient memory for the result string.
[.term]#`+PQescapeBytea+` link:libpq-exec.html#LIBPQ-PQESCAPEBYTEA[#]::
  link:libpq-exec.html#LIBPQ-PQESCAPEBYTEA[`+PQescapeBytea+`] is an older, deprecated version of link:libpq-exec.html#LIBPQ-PQESCAPEBYTEACONN[`+PQescapeByteaConn+`].
  +

  +
  The only difference from link:libpq-exec.html#LIBPQ-PQESCAPEBYTEACONN[`+PQescapeByteaConn+`] is that link:libpq-exec.html#LIBPQ-PQESCAPEBYTEA[`+PQescapeBytea+`] does not take a `+PGconn+` parameter. Because of this, link:libpq-exec.html#LIBPQ-PQESCAPEBYTEA[`+PQescapeBytea+`] can only be used safely in client programs that use a single PostgreSQL connection at a time (in this case it can find out what it needs to know [.quote]#“[.quote]#behind the scenes#”#). It [.emphasis]#_might give the wrong results_# if used in programs that use multiple database connections (use link:libpq-exec.html#LIBPQ-PQESCAPEBYTEACONN[`+PQescapeByteaConn+`] in such cases).
[.term]#`+PQunescapeBytea+` link:libpq-exec.html#LIBPQ-PQUNESCAPEBYTEA[#]::
  Converts a string representation of binary data into binary data — the reverse of link:libpq-exec.html#LIBPQ-PQESCAPEBYTEA[`+PQescapeBytea+`]. This is needed when retrieving `+bytea+` data in text format, but not when retrieving it in binary format.
  +

+
The _`+from+`_ parameter points to a string such as might be returned by link:libpq-exec.html#LIBPQ-PQGETVALUE[`+PQgetvalue+`] when applied to a `+bytea+` column. link:libpq-exec.html#LIBPQ-PQUNESCAPEBYTEA[`+PQunescapeBytea+`] converts this string representation into its binary representation. It returns a pointer to a buffer allocated with `+malloc()+`, or `+NULL+` on error, and puts the size of the buffer in _`+to_length+`_. The result must be freed using link:libpq-misc.html#LIBPQ-PQFREEMEM[`+PQfreemem+`] when it is no longer needed.
+
This conversion is not exactly the inverse of link:libpq-exec.html#LIBPQ-PQESCAPEBYTEA[`+PQescapeBytea+`], because the string is not expected to be [.quote]#“[.quote]#escaped#”# when received from link:libpq-exec.html#LIBPQ-PQGETVALUE[`+PQgetvalue+`]. In particular this means there is no need for string quoting considerations, and so no need for a `+PGconn+` parameter.