Na}{

Path: ~//opt/alt/postgresql11/usr/share/doc/alt-postgresql11-9.2.24/html/

File Content: libpq-exec.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Command Execution Functions</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REV="MADE"
HREF="mailto:pgsql-docs@postgresql.org"><LINK
REL="HOME"
TITLE="PostgreSQL 9.2.24 Documentation"
HREF="index.html"><LINK
REL="UP"
TITLE="libpq - C Library"
HREF="libpq.html"><LINK
REL="PREVIOUS"
TITLE="Connection Status Functions"
HREF="libpq-status.html"><LINK
REL="NEXT"
TITLE="Asynchronous Command Processing"
HREF="libpq-async.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="stylesheet.css"><META
HTTP-EQUIV="Content-Type"
CONTENT="text/html; charset=ISO-8859-1"><META
NAME="creation"
CONTENT="2017-11-06T22:43:11"></HEAD
><BODY
CLASS="SECT1"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="5"
ALIGN="center"
VALIGN="bottom"
><A
HREF="index.html"
>PostgreSQL 9.2.24 Documentation</A
></TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
TITLE="Connection Status Functions"
HREF="libpq-status.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
HREF="libpq.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="60%"
ALIGN="center"
VALIGN="bottom"
>Chapter 31. libpq - C Library</TD
><TD
WIDTH="20%"
ALIGN="right"
VALIGN="top"
><A
TITLE="Asynchronous Command Processing"
HREF="libpq-async.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="LIBPQ-EXEC"
>31.3. Command Execution Functions</A
></H1
> Once a connection to a database server has been successfully
 established, the functions described here are used to perform
 SQL queries and commands.
 <DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="LIBPQ-EXEC-MAIN"
>31.3.1. Main Functions</A
></H2
> <DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="LIBPQ-PQEXEC"
></A
><CODE
CLASS="FUNCTION"
>PQexec</CODE
>
 </DT
><DD
> Submits a command to the server and waits for the result.

<PRE
CLASS="SYNOPSIS"
>PGresult *PQexec(PGconn *conn, const char *command);</PRE
>
 Returns a <TT
CLASS="STRUCTNAME"
>PGresult</TT
> 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 <CODE
CLASS="FUNCTION"
>PQresultStatus</CODE
> 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
 <TT
CLASS="SYMBOL"
>PGRES_FATAL_ERROR</TT
>). Use
 <CODE
CLASS="FUNCTION"
>PQerrorMessage</CODE
> to get more information about such
 errors.
 </DD
></DL
></DIV
>

The command string can include multiple SQL commands
 (separated by semicolons). Multiple queries sent in a single
 <CODE
CLASS="FUNCTION"
>PQexec</CODE
> call are processed in a single transaction, unless
 there are explicit <TT
CLASS="COMMAND"
>BEGIN</TT
>/<TT
CLASS="COMMAND"
>COMMIT</TT
>
 commands included in the query string to divide it into multiple
 transactions. Note however that the returned
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> structure describes only the result
 of the last command executed from the string. Should one of the
 commands fail, processing of the string stops with it and the returned
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> describes the error condition.
 <DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="LIBPQ-PQEXECPARAMS"
></A
><CODE
CLASS="FUNCTION"
>PQexecParams</CODE
>
 </DT
><DD
> Submits a command to the server and waits for the result,
 with the ability to pass parameters separately from the SQL
 command text.

<PRE
CLASS="SYNOPSIS"
>PGresult *PQexecParams(PGconn *conn,
 const char *command,
 int nParams,
 const Oid *paramTypes,
 const char * const *paramValues,
 const int *paramLengths,
 const int *paramFormats,
 int resultFormat);</PRE
>
 <CODE
CLASS="FUNCTION"
>PQexecParams</CODE
> is like <CODE
CLASS="FUNCTION"
>PQexec</CODE
>, 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. <CODE
CLASS="FUNCTION"
>PQexecParams</CODE
> is supported only in protocol 3.0 and later
 connections; it will fail when using protocol 2.0.
 The function arguments are:

<DIV
CLASS="VARIABLELIST"
><DL
><DT
><TT
CLASS="PARAMETER"
>conn</TT
></DT
><DD
> The connection object to send the command through.
 </DD
><DT
><TT
CLASS="PARAMETER"
>command</TT
></DT
><DD
> The SQL command string to be executed. If parameters are used,
 they are referred to in the command string as <TT
CLASS="LITERAL"
>$1</TT
>,
 <TT
CLASS="LITERAL"
>$2</TT
>, etc.
 </DD
><DT
><TT
CLASS="PARAMETER"
>nParams</TT
></DT
><DD
> The number of parameters supplied; it is the length of the arrays
 <TT
CLASS="PARAMETER"
>paramTypes[]</TT
>, <TT
CLASS="PARAMETER"
>paramValues[]</TT
>,
 <TT
CLASS="PARAMETER"
>paramLengths[]</TT
>, and <TT
CLASS="PARAMETER"
>paramFormats[]</TT
>. (The
 array pointers can be <TT
CLASS="SYMBOL"
>NULL</TT
> when <TT
CLASS="PARAMETER"
>nParams</TT
>
 is zero.)
 </DD
><DT
><TT
CLASS="PARAMETER"
>paramTypes[]</TT
></DT
><DD
> Specifies, by OID, the data types to be assigned to the
 parameter symbols. If <TT
CLASS="PARAMETER"
>paramTypes</TT
> is
 <TT
CLASS="SYMBOL"
>NULL</TT
>, 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.
 </DD
><DT
><TT
CLASS="PARAMETER"
>paramValues[]</TT
></DT
><DD
> 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).
 </DD
><DT
><TT
CLASS="PARAMETER"
>paramLengths[]</TT
></DT
><DD
> 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.
 </DD
><DT
><TT
CLASS="PARAMETER"
>paramFormats[]</TT
></DT
><DD
> 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 <TT
CLASS="TYPE"
>numeric</TT
> values requires
 knowledge of the server storage format, as implemented
 in
 <TT
CLASS="FILENAME"
>src/backend/utils/adt/numeric.c::numeric_send()</TT
> and
 <TT
CLASS="FILENAME"
>src/backend/utils/adt/numeric.c::numeric_recv()</TT
>.
 </DD
><DT
><TT
CLASS="PARAMETER"
>resultFormat</TT
></DT
><DD
> 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.)
 </DD
></DL
></DIV
>
 </DD
></DL
></DIV
>
 The primary advantage of <CODE
CLASS="FUNCTION"
>PQexecParams</CODE
> over
 <CODE
CLASS="FUNCTION"
>PQexec</CODE
> is that parameter values can be separated from the
 command string, thus avoiding the need for tedious and error-prone
 quoting and escaping.
 Unlike <CODE
CLASS="FUNCTION"
>PQexec</CODE
>, <CODE
CLASS="FUNCTION"
>PQexecParams</CODE
> allows at most
 one SQL command in the given string. (There can be semicolons in it,
 but not more than one nonempty command.) This is a limitation of the
 underlying protocol, but has some usefulness as an extra defense against
 SQL-injection attacks.
 <DIV
CLASS="TIP"
><BLOCKQUOTE
CLASS="TIP"
>Tip: Specifying parameter types via OIDs is tedious, particularly if you prefer
 not to hard-wire particular OID values into your program. However, you can
 avoid doing so even in cases where the server by itself cannot determine the
 type of the parameter, or chooses a different type than you want. In the
 SQL command text, attach an explicit cast to the parameter symbol to show what
 data type you will send. For example:
<PRE
CLASS="PROGRAMLISTING"
>SELECT * FROM mytable WHERE x = $1::bigint;</PRE
>
 This forces parameter <TT
CLASS="LITERAL"
>$1</TT
> to be treated as <TT
CLASS="TYPE"
>bigint</TT
>, whereas
 by default it would be assigned the same type as <TT
CLASS="LITERAL"
>x</TT
>. Forcing the
 parameter type decision, either this way or by specifying a numeric type OID,
 is strongly recommended when sending parameter values in binary format, because
 binary format has less redundancy than text format and so there is less chance
 that the server will detect a type mismatch mistake for you.
 </BLOCKQUOTE
></DIV
> <DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="LIBPQ-PQPREPARE"
></A
><CODE
CLASS="FUNCTION"
>PQprepare</CODE
>
 </DT
><DD
> Submits a request to create a prepared statement with the
 given parameters, and waits for completion.
<PRE
CLASS="SYNOPSIS"
>PGresult *PQprepare(PGconn *conn,
 const char *stmtName,
 const char *query,
 int nParams,
 const Oid *paramTypes);</PRE
>
 <CODE
CLASS="FUNCTION"
>PQprepare</CODE
> creates a prepared statement for later
 execution with <CODE
CLASS="FUNCTION"
>PQexecPrepared</CODE
>. This feature allows
 commands that will be used repeatedly to be parsed and planned just
 once, rather than each time they are executed.
 <CODE
CLASS="FUNCTION"
>PQprepare</CODE
> is supported only in protocol 3.0 and later
 connections; it will fail when using protocol 2.0.
 The function creates a prepared statement named
 <TT
CLASS="PARAMETER"
>stmtName</TT
> from the <TT
CLASS="PARAMETER"
>query</TT
> string, which
 must contain a single SQL command. <TT
CLASS="PARAMETER"
>stmtName</TT
> can be
 <TT
CLASS="LITERAL"
>""</TT
> 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 <TT
CLASS="LITERAL"
>$1</TT
>, <TT
CLASS="LITERAL"
>$2</TT
>, etc.
 <TT
CLASS="PARAMETER"
>nParams</TT
> is the number of parameters for which types
 are pre-specified in the array <TT
CLASS="PARAMETER"
>paramTypes[]</TT
>. (The
 array pointer can be <TT
CLASS="SYMBOL"
>NULL</TT
> when
 <TT
CLASS="PARAMETER"
>nParams</TT
> is zero.) <TT
CLASS="PARAMETER"
>paramTypes[]</TT
>
 specifies, by OID, the data types to be assigned to the parameter
 symbols. If <TT
CLASS="PARAMETER"
>paramTypes</TT
> is <TT
CLASS="SYMBOL"
>NULL</TT
>,
 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 <TT
CLASS="PARAMETER"
>nParams</TT
>; data types
 will be inferred for these symbols as well. (See
 <CODE
CLASS="FUNCTION"
>PQdescribePrepared</CODE
> for a means to find out
 what data types were inferred.)
 As with <CODE
CLASS="FUNCTION"
>PQexec</CODE
>, the result is normally a
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> 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
 <CODE
CLASS="FUNCTION"
>PQerrorMessage</CODE
> to get more information about
 such errors.
 </DD
></DL
></DIV
>

Prepared statements for use with <CODE
CLASS="FUNCTION"
>PQexecPrepared</CODE
> can also
 be created by executing SQL <A
HREF="sql-prepare.html"
>PREPARE</A
>
 statements. Also, although there is no libpq
 function for deleting a prepared statement, the SQL <A
HREF="sql-deallocate.html"
>DEALLOCATE</A
> statement
 can be used for that purpose.
 <DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="LIBPQ-PQEXECPREPARED"
></A
><CODE
CLASS="FUNCTION"
>PQexecPrepared</CODE
>
 </DT
><DD
> Sends a request to execute a prepared statement with given
 parameters, and waits for the result.
<PRE
CLASS="SYNOPSIS"
>PGresult *PQexecPrepared(PGconn *conn,
 const char *stmtName,
 int nParams,
 const char * const *paramValues,
 const int *paramLengths,
 const int *paramFormats,
 int resultFormat);</PRE
>
 <CODE
CLASS="FUNCTION"
>PQexecPrepared</CODE
> is like <CODE
CLASS="FUNCTION"
>PQexecParams</CODE
>,
 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. <CODE
CLASS="FUNCTION"
>PQexecPrepared</CODE
> is supported
 only in protocol 3.0 and later connections; it will fail when
 using protocol 2.0.
 The parameters are identical to <CODE
CLASS="FUNCTION"
>PQexecParams</CODE
>, except that the
 name of a prepared statement is given instead of a query string, and the
 <TT
CLASS="PARAMETER"
>paramTypes[]</TT
> parameter is not present (it is not needed since
 the prepared statement's parameter types were determined when it was created).
 </DD
><DT
><A
NAME="LIBPQ-PQDESCRIBEPREPARED"
></A
><CODE
CLASS="FUNCTION"
>PQdescribePrepared</CODE
>
 </DT
><DD
> Submits a request to obtain information about the specified
 prepared statement, and waits for completion.
<PRE
CLASS="SYNOPSIS"
>PGresult *PQdescribePrepared(PGconn *conn, const char *stmtName);</PRE
>
 <CODE
CLASS="FUNCTION"
>PQdescribePrepared</CODE
> allows an application to obtain
 information about a previously prepared statement.
 <CODE
CLASS="FUNCTION"
>PQdescribePrepared</CODE
> is supported only in protocol 3.0
 and later connections; it will fail when using protocol 2.0.
 <TT
CLASS="PARAMETER"
>stmtName</TT
> can be <TT
CLASS="LITERAL"
>""</TT
> or <TT
CLASS="SYMBOL"
>NULL</TT
> to reference
 the unnamed statement, otherwise it must be the name of an existing
 prepared statement. On success, a <TT
CLASS="STRUCTNAME"
>PGresult</TT
> with
 status <TT
CLASS="LITERAL"
>PGRES_COMMAND_OK</TT
> is returned. The
 functions <CODE
CLASS="FUNCTION"
>PQnparams</CODE
> and
 <CODE
CLASS="FUNCTION"
>PQparamtype</CODE
> can be applied to this
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> to obtain information about the parameters
 of the prepared statement, and the functions
 <CODE
CLASS="FUNCTION"
>PQnfields</CODE
>, <CODE
CLASS="FUNCTION"
>PQfname</CODE
>,
 <CODE
CLASS="FUNCTION"
>PQftype</CODE
>, etc provide information about the
 result columns (if any) of the statement.
 </DD
><DT
><A
NAME="LIBPQ-PQDESCRIBEPORTAL"
></A
><CODE
CLASS="FUNCTION"
>PQdescribePortal</CODE
>
 </DT
><DD
> Submits a request to obtain information about the specified
 portal, and waits for completion.
<PRE
CLASS="SYNOPSIS"
>PGresult *PQdescribePortal(PGconn *conn, const char *portalName);</PRE
>
 <CODE
CLASS="FUNCTION"
>PQdescribePortal</CODE
> 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 <TT
CLASS="COMMAND"
>DECLARE CURSOR</TT
> SQL command.)
 <CODE
CLASS="FUNCTION"
>PQdescribePortal</CODE
> is supported only in protocol 3.0
 and later connections; it will fail when using protocol 2.0.
 <TT
CLASS="PARAMETER"
>portalName</TT
> can be <TT
CLASS="LITERAL"
>""</TT
> or <TT
CLASS="SYMBOL"
>NULL</TT
> to reference
 the unnamed portal, otherwise it must be the name of an existing
 portal. On success, a <TT
CLASS="STRUCTNAME"
>PGresult</TT
> with status
 <TT
CLASS="LITERAL"
>PGRES_COMMAND_OK</TT
> is returned. The functions
 <CODE
CLASS="FUNCTION"
>PQnfields</CODE
>, <CODE
CLASS="FUNCTION"
>PQfname</CODE
>,
 <CODE
CLASS="FUNCTION"
>PQftype</CODE
>, etc can be applied to the
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> to obtain information about the result
 columns (if any) of the portal.
 </DD
></DL
></DIV
>
 The <TT
CLASS="STRUCTNAME"
>PGresult</TT
>
 structure encapsulates the result returned by the server.
 libpq application programmers should be
 careful to maintain the <TT
CLASS="STRUCTNAME"
>PGresult</TT
> abstraction.
 Use the accessor functions below to get at the contents of
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
>. Avoid directly referencing the
 fields of the <TT
CLASS="STRUCTNAME"
>PGresult</TT
> structure because they
 are subject to change in the future.

<DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="LIBPQ-PQRESULTSTATUS"
></A
><CODE
CLASS="FUNCTION"
>PQresultStatus</CODE
>
 </DT
><DD
> Returns the result status of the command.
<PRE
CLASS="SYNOPSIS"
>ExecStatusType PQresultStatus(const PGresult *res);</PRE
>
 <CODE
CLASS="FUNCTION"
>PQresultStatus</CODE
> can return one of the following values:

<DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="LIBPQ-PGRES-EMPTY-QUERY"
></A
><TT
CLASS="LITERAL"
>PGRES_EMPTY_QUERY</TT
></DT
><DD
> The string sent to the server was empty.
 </DD
><DT
><A
NAME="LIBPQ-PGRES-COMMAND-OK"
></A
><TT
CLASS="LITERAL"
>PGRES_COMMAND_OK</TT
></DT
><DD
> Successful completion of a command returning no data.
 </DD
><DT
><A
NAME="LIBPQ-PGRES-TUPLES-OK"
></A
><TT
CLASS="LITERAL"
>PGRES_TUPLES_OK</TT
></DT
><DD
> Successful completion of a command returning data (such as
 a <TT
CLASS="COMMAND"
>SELECT</TT
> or <TT
CLASS="COMMAND"
>SHOW</TT
>).
 </DD
><DT
><A
NAME="LIBPQ-PGRES-COPY-OUT"
></A
><TT
CLASS="LITERAL"
>PGRES_COPY_OUT</TT
></DT
><DD
> Copy Out (from server) data transfer started.
 </DD
><DT
><A
NAME="LIBPQ-PGRES-COPY-IN"
></A
><TT
CLASS="LITERAL"
>PGRES_COPY_IN</TT
></DT
><DD
> Copy In (to server) data transfer started.
 </DD
><DT
><A
NAME="LIBPQ-PGRES-BAD-RESPONSE"
></A
><TT
CLASS="LITERAL"
>PGRES_BAD_RESPONSE</TT
></DT
><DD
> The server's response was not understood.
 </DD
><DT
><A
NAME="LIBPQ-PGRES-NONFATAL-ERROR"
></A
><TT
CLASS="LITERAL"
>PGRES_NONFATAL_ERROR</TT
></DT
><DD
> A nonfatal error (a notice or warning) occurred.
 </DD
><DT
><A
NAME="LIBPQ-PGRES-FATAL-ERROR"
></A
><TT
CLASS="LITERAL"
>PGRES_FATAL_ERROR</TT
></DT
><DD
> A fatal error occurred.
 </DD
><DT
><A
NAME="LIBPQ-PGRES-COPY-BOTH"
></A
><TT
CLASS="LITERAL"
>PGRES_COPY_BOTH</TT
></DT
><DD
> 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.
 </DD
><DT
><A
NAME="LIBPQ-PGRES-SINGLE-TUPLE"
></A
><TT
CLASS="LITERAL"
>PGRES_SINGLE_TUPLE</TT
></DT
><DD
> The <TT
CLASS="STRUCTNAME"
>PGresult</TT
> contains a single result tuple
 from the current command. This status occurs only when
 single-row mode has been selected for the query
 (see <A
HREF="libpq-single-row-mode.html"
>Section 31.5</A
>).
 </DD
></DL
></DIV
>

If the result status is <TT
CLASS="LITERAL"
>PGRES_TUPLES_OK</TT
> or
 <TT
CLASS="LITERAL"
>PGRES_SINGLE_TUPLE</TT
>, then
 the functions described below can be used to retrieve the rows
 returned by the query. Note that a <TT
CLASS="COMMAND"
>SELECT</TT
>
 command that happens to retrieve zero rows still shows
 <TT
CLASS="LITERAL"
>PGRES_TUPLES_OK</TT
>.
 <TT
CLASS="LITERAL"
>PGRES_COMMAND_OK</TT
> is for commands that can never
 return rows (<TT
CLASS="COMMAND"
>INSERT</TT
>, <TT
CLASS="COMMAND"
>UPDATE</TT
>,
 etc.). A response of <TT
CLASS="LITERAL"
>PGRES_EMPTY_QUERY</TT
> might
 indicate a bug in the client software.
 A result of status <TT
CLASS="SYMBOL"
>PGRES_NONFATAL_ERROR</TT
> will
 never be returned directly by <CODE
CLASS="FUNCTION"
>PQexec</CODE
> or other
 query execution functions; results of this kind are instead passed
 to the notice processor (see <A
HREF="libpq-notice-processing.html"
>Section 31.12</A
>).
 </DD
><DT
><A
NAME="LIBPQ-PQRESSTATUS"
></A
><CODE
CLASS="FUNCTION"
>PQresStatus</CODE
>
 </DT
><DD
> Converts the enumerated type returned by
 <CODE
CLASS="FUNCTION"
>PQresultStatus</CODE
> into a string constant describing the
 status code. The caller should not free the result.

<PRE
CLASS="SYNOPSIS"
>char *PQresStatus(ExecStatusType status);</PRE
>
 </DD
><DT
><A
NAME="LIBPQ-PQRESULTERRORMESSAGE"
></A
><CODE
CLASS="FUNCTION"
>PQresultErrorMessage</CODE
>
 </DT
><DD
> Returns the error message associated with the command, or an empty string
 if there was no error.
<PRE
CLASS="SYNOPSIS"
>char *PQresultErrorMessage(const PGresult *res);</PRE
>
 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 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> handle is
 passed to <CODE
CLASS="FUNCTION"
>PQclear</CODE
>.
 Immediately following a <CODE
CLASS="FUNCTION"
>PQexec</CODE
> or
 <CODE
CLASS="FUNCTION"
>PQgetResult</CODE
> call,
 <CODE
CLASS="FUNCTION"
>PQerrorMessage</CODE
> (on the connection) will return
 the same string as <CODE
CLASS="FUNCTION"
>PQresultErrorMessage</CODE
> (on
 the result). However, a <TT
CLASS="STRUCTNAME"
>PGresult</TT
> will
 retain its error message until destroyed, whereas the connection's
 error message will change when subsequent operations are done.
 Use <CODE
CLASS="FUNCTION"
>PQresultErrorMessage</CODE
> when you want to
 know the status associated with a particular
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
>; use
 <CODE
CLASS="FUNCTION"
>PQerrorMessage</CODE
> when you want to know the
 status from the latest operation on the connection.
 </DD
><DT
><A
NAME="LIBPQ-PQRESULTERRORFIELD"
></A
><CODE
CLASS="FUNCTION"
>PQresultErrorField</CODE
></DT
><DD
> Returns an individual field of an error report.
<PRE
CLASS="SYNOPSIS"
>char *PQresultErrorField(const PGresult *res, int fieldcode);</PRE
>
 <TT
CLASS="PARAMETER"
>fieldcode</TT
> is an error field identifier; see the symbols
 listed below. <TT
CLASS="SYMBOL"
>NULL</TT
> is returned if the
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> 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 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> handle is passed to
 <CODE
CLASS="FUNCTION"
>PQclear</CODE
>.
 The following field codes are available:
 <DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="LIBPQ-PG-DIAG-SEVERITY"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_SEVERITY</TT
></DT
><DD
> The severity; the field contents are <TT
CLASS="LITERAL"
>ERROR</TT
>,
 <TT
CLASS="LITERAL"
>FATAL</TT
>, or <TT
CLASS="LITERAL"
>PANIC</TT
> (in an error message),
 or <TT
CLASS="LITERAL"
>WARNING</TT
>, <TT
CLASS="LITERAL"
>NOTICE</TT
>, <TT
CLASS="LITERAL"
>DEBUG</TT
>,
 <TT
CLASS="LITERAL"
>INFO</TT
>, or <TT
CLASS="LITERAL"
>LOG</TT
> (in a notice message), or
 a localized translation of one of these. Always present.
 </DD
><DT
><A
NAME="LIBPQ-PG-DIAG-SQLSTATE"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_SQLSTATE</TT
></DT
><DD
> 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 <A
HREF="errcodes-appendix.html"
>Appendix A</A
>. This field is not localizable,
 and is always present.
 </DD
><DT
><A
NAME="LIBPQ-PG-DIAG-MESSAGE-PRIMARY"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_MESSAGE_PRIMARY</TT
></DT
><DD
> The primary human-readable error message (typically one line).
 Always present.
 </DD
><DT
><A
NAME="LIBPQ-PG-DIAG-MESSAGE-DETAIL"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_MESSAGE_DETAIL</TT
></DT
><DD
> Detail: an optional secondary error message carrying more
 detail about the problem. Might run to multiple lines.
 </DD
><DT
><A
NAME="LIBPQ-PG-DIAG-MESSAGE-HINT"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_MESSAGE_HINT</TT
></DT
><DD
> 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.
 </DD
><DT
><A
NAME="LIBPQ-PG-DIAG-STATEMENT-POSITION"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_STATEMENT_POSITION</TT
></DT
><DD
> 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.
 </DD
><DT
><A
NAME="LIBPQ-PG-DIAG-INTERNAL-POSITION"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_INTERNAL_POSITION</TT
></DT
><DD
> This is defined the same as the
 <TT
CLASS="SYMBOL"
>PG_DIAG_STATEMENT_POSITION</TT
> field, but it is used
 when the cursor position refers to an internally generated
 command rather than the one submitted by the client. The
 <TT
CLASS="SYMBOL"
>PG_DIAG_INTERNAL_QUERY</TT
> field will always appear when
 this field appears.
 </DD
><DT
><A
NAME="LIBPQ-PG-DIAG-INTERNAL-QUERY"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_INTERNAL_QUERY</TT
></DT
><DD
> The text of a failed internally-generated command. This could
 be, for example, a SQL query issued by a PL/pgSQL function.
 </DD
><DT
><A
NAME="LIBPQ-PG-DIAG-CONTEXT"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_CONTEXT</TT
></DT
><DD
> 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.
 </DD
><DT
><A
NAME="LIBPQ-PG-DIAG-SOURCE-FILE"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_SOURCE_FILE</TT
></DT
><DD
> The file name of the source-code location where the error was
 reported.
 </DD
><DT
><A
NAME="LIBPQ-PG-DIAG-SOURCE-LINE"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_SOURCE_LINE</TT
></DT
><DD
> The line number of the source-code location where the error
 was reported.
 </DD
><DT
><A
NAME="LIBPQ-PG-DIAG-SOURCE-FUNCTION"
></A
><TT
CLASS="SYMBOL"
>PG_DIAG_SOURCE_FUNCTION</TT
></DT
><DD
> The name of the source-code function reporting the error.
 </DD
></DL
></DIV
>
 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.
 Errors returned by a pre-3.0-protocol server will include severity and
 primary message, and sometimes a detail message, but no other fields.
 Note that error fields are only available from
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> objects, not
 <TT
CLASS="STRUCTNAME"
>PGconn</TT
> objects; there is no
 <CODE
CLASS="FUNCTION"
>PQerrorField</CODE
> function.
 </DD
><DT
><A
NAME="LIBPQ-PQCLEAR"
></A
><CODE
CLASS="FUNCTION"
>PQclear</CODE
></DT
><DD
> Frees the storage associated with a
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
>. Every command result should be
 freed via <CODE
CLASS="FUNCTION"
>PQclear</CODE
> when it is no longer
 needed.

<PRE
CLASS="SYNOPSIS"
>void PQclear(PGresult *res);</PRE
>
 You can keep a <TT
CLASS="STRUCTNAME"
>PGresult</TT
> 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 <CODE
CLASS="FUNCTION"
>PQclear</CODE
>. Failure to do this
 will result in memory leaks in your application.
 </DD
></DL
></DIV
>
 </DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="LIBPQ-EXEC-SELECT-INFO"
>31.3.2. Retrieving Query Result Information</A
></H2
> These functions are used to extract information from a
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> object that represents a successful
 query result (that is, one that has status
 <TT
CLASS="LITERAL"
>PGRES_TUPLES_OK</TT
> or <TT
CLASS="LITERAL"
>PGRES_SINGLE_TUPLE</TT
>).
 They can also be used to extract
 information from a successful Describe operation: a Describe's result
 has all the same column information that actual execution of the query
 would provide, but it has zero rows. For objects with other status values,
 these functions will act as though the result has zero rows and zero columns.
 <DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="LIBPQ-PQNTUPLES"
></A
><CODE
CLASS="FUNCTION"
>PQntuples</CODE
>
 </DT
><DD
> Returns the number of rows (tuples) in the query result.
 (Note that <TT
CLASS="STRUCTNAME"
>PGresult</TT
> objects are limited to no more
 than <TT
CLASS="LITERAL"
>INT_MAX</TT
> rows, so an <TT
CLASS="TYPE"
>int</TT
> result is
 sufficient.)

<PRE
CLASS="SYNOPSIS"
>int PQntuples(const PGresult *res);</PRE
>

</DD
><DT
><A
NAME="LIBPQ-PQNFIELDS"
></A
><CODE
CLASS="FUNCTION"
>PQnfields</CODE
>
 </DT
><DD
> Returns the number of columns (fields) in each row of the query
 result.

<PRE
CLASS="SYNOPSIS"
>int PQnfields(const PGresult *res);</PRE
>
 </DD
><DT
><A
NAME="LIBPQ-PQFNAME"
></A
><CODE
CLASS="FUNCTION"
>PQfname</CODE
>
 </DT
><DD
> Returns the column name associated with the given column number.
 Column numbers start at 0. The caller should not free the result
 directly. It will be freed when the associated
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> handle is passed to
 <CODE
CLASS="FUNCTION"
>PQclear</CODE
>.
<PRE
CLASS="SYNOPSIS"
>char *PQfname(const PGresult *res,
 int column_number);</PRE
>
 <TT
CLASS="SYMBOL"
>NULL</TT
> is returned if the column number is out of range.
 </DD
><DT
><A
NAME="LIBPQ-PQFNUMBER"
></A
><CODE
CLASS="FUNCTION"
>PQfnumber</CODE
>
 </DT
><DD
> Returns the column number associated with the given column name.
<PRE
CLASS="SYNOPSIS"
>int PQfnumber(const PGresult *res,
 const char *column_name);</PRE
>
 -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:
<PRE
CLASS="PROGRAMLISTING"
>SELECT 1 AS FOO, 2 AS "BAR";</PRE
>
 we would have the results:
<PRE
CLASS="PROGRAMLISTING"
>PQfname(res, 0) foo
PQfname(res, 1) BAR
PQfnumber(res, "FOO") 0
PQfnumber(res, "foo") 0
PQfnumber(res, "BAR") -1
PQfnumber(res, "\"BAR\"") 1</PRE
>
 </DD
><DT
><A
NAME="LIBPQ-PQFTABLE"
></A
><CODE
CLASS="FUNCTION"
>PQftable</CODE
>
 </DT
><DD
> Returns the OID of the table from which the given column was
 fetched. Column numbers start at 0.
<PRE
CLASS="SYNOPSIS"
>Oid PQftable(const PGresult *res,
 int column_number);</PRE
>
 <TT
CLASS="LITERAL"
>InvalidOid</TT
> is returned if the column number is out of range,
 or if the specified column is not a simple reference to a table column,
 or when using pre-3.0 protocol.
 You can query the system table <TT
CLASS="LITERAL"
>pg_class</TT
> to determine
 exactly which table is referenced.
 The type <TT
CLASS="TYPE"
>Oid</TT
> and the constant
 <TT
CLASS="LITERAL"
>InvalidOid</TT
> will be defined when you include
 the libpq header file. They will both
 be some integer type.
 </DD
><DT
><A
NAME="LIBPQ-PQFTABLECOL"
></A
><CODE
CLASS="FUNCTION"
>PQftablecol</CODE
>
 </DT
><DD
> 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.
<PRE
CLASS="SYNOPSIS"
>int PQftablecol(const PGresult *res,
 int column_number);</PRE
>
 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, or
 when using pre-3.0 protocol.
 </DD
><DT
><A
NAME="LIBPQ-PQFFORMAT"
></A
><CODE
CLASS="FUNCTION"
>PQfformat</CODE
>
 </DT
><DD
> Returns the format code indicating the format of the given
 column. Column numbers start at 0.
<PRE
CLASS="SYNOPSIS"
>int PQfformat(const PGresult *res,
 int column_number);</PRE
>
 Format code zero indicates textual data representation, while format
 code one indicates binary representation. (Other codes are reserved
 for future definition.)
 </DD
><DT
><A
NAME="LIBPQ-PQFTYPE"
></A
><CODE
CLASS="FUNCTION"
>PQftype</CODE
>
 </DT
><DD
> 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.
<PRE
CLASS="SYNOPSIS"
>Oid PQftype(const PGresult *res,
 int column_number);</PRE
>
 You can query the system table <TT
CLASS="LITERAL"
>pg_type</TT
> to
 obtain the names and properties of the various data types. The
 <ACRONYM
CLASS="ACRONYM"
>OID</ACRONYM
>s of the built-in data types are defined
 in the file <TT
CLASS="FILENAME"
>src/include/catalog/pg_type.h</TT
>
 in the source tree.
 </DD
><DT
><A
NAME="LIBPQ-PQFMOD"
></A
><CODE
CLASS="FUNCTION"
>PQfmod</CODE
>
 </DT
><DD
> Returns the type modifier of the column associated with the
 given column number. Column numbers start at 0.
<PRE
CLASS="SYNOPSIS"
>int PQfmod(const PGresult *res,
 int column_number);</PRE
>
 The interpretation of modifier values is type-specific; they
 typically indicate precision or size limits. The value -1 is
 used to indicate "no information available". Most data
 types do not use modifiers, in which case the value is always
 -1.
 </DD
><DT
><A
NAME="LIBPQ-PQFSIZE"
></A
><CODE
CLASS="FUNCTION"
>PQfsize</CODE
>
 </DT
><DD
> Returns the size in bytes of the column associated with the
 given column number. Column numbers start at 0.
<PRE
CLASS="SYNOPSIS"
>int PQfsize(const PGresult *res,
 int column_number);</PRE
>
 <CODE
CLASS="FUNCTION"
>PQfsize</CODE
> 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.
 </DD
><DT
><A
NAME="LIBPQ-PQBINARYTUPLES"
></A
><CODE
CLASS="FUNCTION"
>PQbinaryTuples</CODE
>
 </DT
><DD
> Returns 1 if the <TT
CLASS="STRUCTNAME"
>PGresult</TT
> contains binary data
 and 0 if it contains text data.
<PRE
CLASS="SYNOPSIS"
>int PQbinaryTuples(const PGresult *res);</PRE
>
 This function is deprecated (except for its use in connection with
 <TT
CLASS="COMMAND"
>COPY</TT
>), because it is possible for a single
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> to contain text data in some columns and
 binary data in others. <CODE
CLASS="FUNCTION"
>PQfformat</CODE
> is preferred.
 <CODE
CLASS="FUNCTION"
>PQbinaryTuples</CODE
> returns 1 only if all columns of the
 result are binary (format 1).
 </DD
><DT
><A
NAME="LIBPQ-PQGETVALUE"
></A
><CODE
CLASS="FUNCTION"
>PQgetvalue</CODE
>
 </DT
><DD
> Returns a single field value of one row of a
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
>. Row and column numbers start
 at 0. The caller should not free the result directly. It will
 be freed when the associated <TT
CLASS="STRUCTNAME"
>PGresult</TT
> handle is
 passed to <CODE
CLASS="FUNCTION"
>PQclear</CODE
>.
<PRE
CLASS="SYNOPSIS"
>char *PQgetvalue(const PGresult *res,
 int row_number,
 int column_number);</PRE
>
 For data in text format, the value returned by
 <CODE
CLASS="FUNCTION"
>PQgetvalue</CODE
> 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 <CODE
CLASS="FUNCTION"
>typsend</CODE
> and <CODE
CLASS="FUNCTION"
>typreceive</CODE
>
 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
 <CODE
CLASS="FUNCTION"
>PQgetisnull</CODE
> to distinguish null values from
 empty-string values.
 The pointer returned by <CODE
CLASS="FUNCTION"
>PQgetvalue</CODE
> points
 to storage that is part of the <TT
CLASS="STRUCTNAME"
>PGresult</TT
>
 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 <TT
CLASS="STRUCTNAME"
>PGresult</TT
>
 structure itself.
 </DD
><DT
><A
NAME="LIBPQ-PQGETISNULL"
></A
><CODE
CLASS="FUNCTION"
>PQgetisnull</CODE
>
 
 </DT
><DD
> Tests a field for a null value. Row and column numbers start
 at 0.
<PRE
CLASS="SYNOPSIS"
>int PQgetisnull(const PGresult *res,
 int row_number,
 int column_number);</PRE
>
 This function returns 1 if the field is null and 0 if it
 contains a non-null value. (Note that
 <CODE
CLASS="FUNCTION"
>PQgetvalue</CODE
> will return an empty string,
 not a null pointer, for a null field.)
 </DD
><DT
><A
NAME="LIBPQ-PQGETLENGTH"
></A
><CODE
CLASS="FUNCTION"
>PQgetlength</CODE
>
 </DT
><DD
> Returns the actual length of a field value in bytes. Row and
 column numbers start at 0.
<PRE
CLASS="SYNOPSIS"
>int PQgetlength(const PGresult *res,
 int row_number,
 int column_number);</PRE
>
 This is the actual data length for the particular data value,
 that is, the size of the object pointed to by
 <CODE
CLASS="FUNCTION"
>PQgetvalue</CODE
>. For text data format this is
 the same as <CODE
CLASS="FUNCTION"
>strlen()</CODE
>. For binary format this is
 essential information. Note that one should not
 rely on <CODE
CLASS="FUNCTION"
>PQfsize</CODE
> to obtain the actual data
 length.
 </DD
><DT
><A
NAME="LIBPQ-PQNPARAMS"
></A
><CODE
CLASS="FUNCTION"
>PQnparams</CODE
>
 </DT
><DD
> Returns the number of parameters of a prepared statement.
<PRE
CLASS="SYNOPSIS"
>int PQnparams(const PGresult *res);</PRE
>
 This function is only useful when inspecting the result of
 <CODE
CLASS="FUNCTION"
>PQdescribePrepared</CODE
>. For other types of queries it
 will return zero.
 </DD
><DT
><A
NAME="LIBPQ-PQPARAMTYPE"
></A
><CODE
CLASS="FUNCTION"
>PQparamtype</CODE
>
 </DT
><DD
> Returns the data type of the indicated statement parameter.
 Parameter numbers start at 0.
<PRE
CLASS="SYNOPSIS"
>Oid PQparamtype(const PGresult *res, int param_number);</PRE
>
 This function is only useful when inspecting the result of
 <CODE
CLASS="FUNCTION"
>PQdescribePrepared</CODE
>. For other types of queries it
 will return zero.
 </DD
><DT
><A
NAME="LIBPQ-PQPRINT"
></A
><CODE
CLASS="FUNCTION"
>PQprint</CODE
>
 </DT
><DD
> Prints out all the rows and, optionally, the column names to
 the specified output stream.
<PRE
CLASS="SYNOPSIS"
>void PQprint(FILE *fout, /* output stream */
 const PGresult *res,
 const PQprintOpt *po);
typedef struct
{
 pqbool header; /* print output field headings and row count */
 pqbool align; /* fill align the fields */
 pqbool standard; /* old brain dead format */
 pqbool html3; /* output HTML tables */
 pqbool expanded; /* expand tables */
 pqbool pager; /* use pager for output if needed */
 char *fieldSep; /* field separator */
 char *tableOpt; /* attributes for HTML table element */
 char *caption; /* HTML table caption */
 char **fieldName; /* null-terminated array of replacement field names */
} PQprintOpt;</PRE
>
 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.
 </DD
></DL
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="LIBPQ-EXEC-NONSELECT"
>31.3.3. Retrieving Other Result Information</A
></H2
> These functions are used to extract other information from
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> objects.
 <DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="LIBPQ-PQCMDSTATUS"
></A
><CODE
CLASS="FUNCTION"
>PQcmdStatus</CODE
>
 </DT
><DD
> Returns the command status tag from the SQL command that generated
 the <TT
CLASS="STRUCTNAME"
>PGresult</TT
>.
<PRE
CLASS="SYNOPSIS"
>char *PQcmdStatus(PGresult *res);</PRE
>
 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 <TT
CLASS="STRUCTNAME"
>PGresult</TT
> handle is passed to
 <CODE
CLASS="FUNCTION"
>PQclear</CODE
>.
 </DD
><DT
><A
NAME="LIBPQ-PQCMDTUPLES"
></A
><CODE
CLASS="FUNCTION"
>PQcmdTuples</CODE
>
 </DT
><DD
> Returns the number of rows affected by the SQL command.
<PRE
CLASS="SYNOPSIS"
>char *PQcmdTuples(PGresult *res);</PRE
>
 This function returns a string containing the number of rows
 affected by the <ACRONYM
CLASS="ACRONYM"
>SQL</ACRONYM
> statement that generated the
 <TT
CLASS="STRUCTNAME"
>PGresult</TT
>. This function can only be used following
 the execution of a <TT
CLASS="COMMAND"
>SELECT</TT
>, <TT
CLASS="COMMAND"
>CREATE TABLE AS</TT
>,
 <TT
CLASS="COMMAND"
>INSERT</TT
>, <TT
CLASS="COMMAND"
>UPDATE</TT
>, <TT
CLASS="COMMAND"
>DELETE</TT
>,
 <TT
CLASS="COMMAND"
>MOVE</TT
>, <TT
CLASS="COMMAND"
>FETCH</TT
>, or <TT
CLASS="COMMAND"
>COPY</TT
> statement,
 or an <TT
CLASS="COMMAND"
>EXECUTE</TT
> of a prepared query that contains an
 <TT
CLASS="COMMAND"
>INSERT</TT
>, <TT
CLASS="COMMAND"
>UPDATE</TT
>, or <TT
CLASS="COMMAND"
>DELETE</TT
> statement.
 If the command that generated the <TT
CLASS="STRUCTNAME"
>PGresult</TT
> was anything
 else, <CODE
CLASS="FUNCTION"
>PQcmdTuples</CODE
> returns an empty string. The caller
 should not free the return value directly. It will be freed when
 the associated <TT
CLASS="STRUCTNAME"
>PGresult</TT
> handle is passed to
 <CODE
CLASS="FUNCTION"
>PQclear</CODE
>.
 </DD
><DT
><A
NAME="LIBPQ-PQOIDVALUE"
></A
><CODE
CLASS="FUNCTION"
>PQoidValue</CODE
>
 </DT
><DD
> Returns the OID
 of the inserted row, if the <ACRONYM
CLASS="ACRONYM"
>SQL</ACRONYM
> command was an
 <TT
CLASS="COMMAND"
>INSERT</TT
> that inserted exactly one row into a table that
 has OIDs, or a <TT
CLASS="COMMAND"
>EXECUTE</TT
> of a prepared query containing
 a suitable <TT
CLASS="COMMAND"
>INSERT</TT
> statement. Otherwise, this function
 returns <TT
CLASS="LITERAL"
>InvalidOid</TT
>. This function will also
 return <TT
CLASS="LITERAL"
>InvalidOid</TT
> if the table affected by the
 <TT
CLASS="COMMAND"
>INSERT</TT
> statement does not contain OIDs.
<PRE
CLASS="SYNOPSIS"
>Oid PQoidValue(const PGresult *res);</PRE
>
 </DD
><DT
><A
NAME="LIBPQ-PQOIDSTATUS"
></A
><CODE
CLASS="FUNCTION"
>PQoidStatus</CODE
>
 </DT
><DD
> This function is deprecated in favor of
 <CODE
CLASS="FUNCTION"
>PQoidValue</CODE
> and is not thread-safe.
 It returns a string with the OID of the inserted row, while
 <CODE
CLASS="FUNCTION"
>PQoidValue</CODE
> returns the OID value.
<PRE
CLASS="SYNOPSIS"
>char *PQoidStatus(const PGresult *res);</PRE
>
 </DD
></DL
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="LIBPQ-EXEC-ESCAPE-STRING"
>31.3.4. Escaping Strings for Inclusion in SQL Commands</A
></H2
><DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="LIBPQ-PQESCAPELITERAL"
></A
><CODE
CLASS="FUNCTION"
>PQescapeLiteral</CODE
>
 </DT
><DD
><PRE
CLASS="SYNOPSIS"
>char *PQescapeLiteral(PGconn *conn, const char *str, size_t length);</PRE
>
 <CODE
CLASS="FUNCTION"
>PQescapeLiteral</CODE
> 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.
 <CODE
CLASS="FUNCTION"
>PQescapeLiteral</CODE
> performs this operation.
 <CODE
CLASS="FUNCTION"
>PQescapeLiteral</CODE
> returns an escaped version of the
 <TT
CLASS="PARAMETER"
>str</TT
> parameter in memory allocated with
 <CODE
CLASS="FUNCTION"
>malloc()</CODE
>. This memory should be freed using
 <CODE
CLASS="FUNCTION"
>PQfreemem()</CODE
> when the result is no longer needed.
 A terminating zero byte is not required, and should not be
 counted in <TT
CLASS="PARAMETER"
>length</TT
>. (If a terminating zero byte is found
 before <TT
CLASS="PARAMETER"
>length</TT
> bytes are processed,
 <CODE
CLASS="FUNCTION"
>PQescapeLiteral</CODE
> stops at the zero; the behavior is
 thus rather like <CODE
CLASS="FUNCTION"
>strncpy</CODE
>.) 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, <CODE
CLASS="FUNCTION"
>PQescapeLiteral</CODE
> returns <TT
CLASS="SYMBOL"
>NULL</TT
> and a suitable
 message is stored in the <TT
CLASS="PARAMETER"
>conn</TT
> object.
 <DIV
CLASS="TIP"
><BLOCKQUOTE
CLASS="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
 "SQL injection" attacks wherein unwanted SQL commands are
 fed to your database.
 </BLOCKQUOTE
></DIV
> Note that it is not necessary nor correct to do escaping when a data
 value is passed as a separate parameter in <CODE
CLASS="FUNCTION"
>PQexecParams</CODE
> or
 its sibling routines.
 </DD
><DT
><A
NAME="LIBPQ-PQESCAPEIDENTIFIER"
></A
><CODE
CLASS="FUNCTION"
>PQescapeIdentifier</CODE
>
 </DT
><DD
><PRE
CLASS="SYNOPSIS"
>char *PQescapeIdentifier(PGconn *conn, const char *str, size_t length);</PRE
>
 <CODE
CLASS="FUNCTION"
>PQescapeIdentifier</CODE
> 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.
 <CODE
CLASS="FUNCTION"
>PQescapeIdentifier</CODE
> returns a version of the
 <TT
CLASS="PARAMETER"
>str</TT
> parameter escaped as an SQL identifier
 in memory allocated with <CODE
CLASS="FUNCTION"
>malloc()</CODE
>. This memory must be
 freed using <CODE
CLASS="FUNCTION"
>PQfreemem()</CODE
> when the result is no longer
 needed. A terminating zero byte is not required, and should not be
 counted in <TT
CLASS="PARAMETER"
>length</TT
>. (If a terminating zero byte is found
 before <TT
CLASS="PARAMETER"
>length</TT
> bytes are processed,
 <CODE
CLASS="FUNCTION"
>PQescapeIdentifier</CODE
> stops at the zero; the behavior is
 thus rather like <CODE
CLASS="FUNCTION"
>strncpy</CODE
>.) 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, <CODE
CLASS="FUNCTION"
>PQescapeIdentifier</CODE
> returns <TT
CLASS="SYMBOL"
>NULL</TT
> and a suitable
 message is stored in the <TT
CLASS="PARAMETER"
>conn</TT
> object.
 <DIV
CLASS="TIP"
><BLOCKQUOTE
CLASS="TIP"
>Tip: As with string literals, to prevent SQL injection attacks,
 SQL identifiers must be escaped when they are received from an
 untrustworthy source.
 </BLOCKQUOTE
></DIV
></DD
><DT
><A
NAME="LIBPQ-PQESCAPESTRINGCONN"
></A
><CODE
CLASS="FUNCTION"
>PQescapeStringConn</CODE
>
 </DT
><DD
><PRE
CLASS="SYNOPSIS"
>size_t PQescapeStringConn(PGconn *conn,
 char *to, const char *from, size_t length,
 int *error);</PRE
>
 <CODE
CLASS="FUNCTION"
>PQescapeStringConn</CODE
> escapes string literals, much like
 <CODE
CLASS="FUNCTION"
>PQescapeLiteral</CODE
>. Unlike <CODE
CLASS="FUNCTION"
>PQescapeLiteral</CODE
>,
 the caller is responsible for providing an appropriately sized buffer.
 Furthermore, <CODE
CLASS="FUNCTION"
>PQescapeStringConn</CODE
> 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 <TT
CLASS="PARAMETER"
>from</TT
> points to
 the first character of the string that is to be escaped, and the
 <TT
CLASS="PARAMETER"
>length</TT
> parameter gives the number of bytes in this
 string. A terminating zero byte is not required, and should not be
 counted in <TT
CLASS="PARAMETER"
>length</TT
>. (If a terminating zero byte is found
 before <TT
CLASS="PARAMETER"
>length</TT
> bytes are processed,
 <CODE
CLASS="FUNCTION"
>PQescapeStringConn</CODE
> stops at the zero; the behavior is
 thus rather like <CODE
CLASS="FUNCTION"
>strncpy</CODE
>.) <TT
CLASS="PARAMETER"
>to</TT
> shall point
 to a buffer that is able to hold at least one more byte than twice
 the value of <TT
CLASS="PARAMETER"
>length</TT
>, otherwise the behavior is undefined.
 Behavior is likewise undefined if the <TT
CLASS="PARAMETER"
>to</TT
> and
 <TT
CLASS="PARAMETER"
>from</TT
> strings overlap.
 If the <TT
CLASS="PARAMETER"
>error</TT
> parameter is not <TT
CLASS="SYMBOL"
>NULL</TT
>, then
 <TT
CLASS="LITERAL"
>*error</TT
> 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
 <TT
CLASS="PARAMETER"
>conn</TT
> object, whether or not <TT
CLASS="PARAMETER"
>error</TT
> is <TT
CLASS="SYMBOL"
>NULL</TT
>.
 <CODE
CLASS="FUNCTION"
>PQescapeStringConn</CODE
> returns the number of bytes written
 to <TT
CLASS="PARAMETER"
>to</TT
>, not including the terminating zero byte.
 </DD
><DT
><A
NAME="LIBPQ-PQESCAPESTRING"
></A
><CODE
CLASS="FUNCTION"
>PQescapeString</CODE
>
 </DT
><DD
> <CODE
CLASS="FUNCTION"
>PQescapeString</CODE
> is an older, deprecated version of
 <CODE
CLASS="FUNCTION"
>PQescapeStringConn</CODE
>.
<PRE
CLASS="SYNOPSIS"
>size_t PQescapeString (char *to, const char *from, size_t length);</PRE
>
 The only difference from <CODE
CLASS="FUNCTION"
>PQescapeStringConn</CODE
> is that
 <CODE
CLASS="FUNCTION"
>PQescapeString</CODE
> does not take <TT
CLASS="STRUCTNAME"
>PGconn</TT
>
 or <TT
CLASS="PARAMETER"
>error</TT
> parameters.
 Because of this, it cannot adjust its behavior depending on the
 connection properties (such as character encoding) and therefore
 it might give the wrong results. Also, it has no way
 to report error conditions.
 <CODE
CLASS="FUNCTION"
>PQescapeString</CODE
> 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 "behind the scenes"). In other contexts it is a security
 hazard and should be avoided in favor of
 <CODE
CLASS="FUNCTION"
>PQescapeStringConn</CODE
>.
 </DD
><DT
><A
NAME="LIBPQ-PQESCAPEBYTEACONN"
></A
><CODE
CLASS="FUNCTION"
>PQescapeByteaConn</CODE
>
 </DT
><DD
> Escapes binary data for use within an SQL command with the type
 <TT
CLASS="TYPE"
>bytea</TT
>. As with <CODE
CLASS="FUNCTION"
>PQescapeStringConn</CODE
>,
 this is only used when inserting data directly into an SQL command string.
<PRE
CLASS="SYNOPSIS"
>unsigned char *PQescapeByteaConn(PGconn *conn,
 const unsigned char *from,
 size_t from_length,
 size_t *to_length);</PRE
>
 Certain byte values must be escaped when used as part of a
 <TT
CLASS="TYPE"
>bytea</TT
> literal in an <ACRONYM
CLASS="ACRONYM"
>SQL</ACRONYM
> statement.
 <CODE
CLASS="FUNCTION"
>PQescapeByteaConn</CODE
> escapes bytes using
 either hex encoding or backslash escaping. See <A
HREF="datatype-binary.html"
>Section 8.4</A
> for more information.
 The <TT
CLASS="PARAMETER"
>from</TT
> parameter points to the first
 byte of the string that is to be escaped, and the
 <TT
CLASS="PARAMETER"
>from_length</TT
> parameter gives the number of
 bytes in this binary string. (A terminating zero byte is
 neither necessary nor counted.) The <TT
CLASS="PARAMETER"
>to_length</TT
>
 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.
 <CODE
CLASS="FUNCTION"
>PQescapeByteaConn</CODE
> returns an escaped version of the
 <TT
CLASS="PARAMETER"
>from</TT
> parameter binary string in memory
 allocated with <CODE
CLASS="FUNCTION"
>malloc()</CODE
>. This memory should be freed using
 <CODE
CLASS="FUNCTION"
>PQfreemem()</CODE
> 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 <TT
CLASS="TYPE"
>bytea</TT
> 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 <TT
CLASS="PARAMETER"
>conn</TT
> object. Currently, the only
 possible error is insufficient memory for the result string.
 </DD
><DT
><A
NAME="LIBPQ-PQESCAPEBYTEA"
></A
><CODE
CLASS="FUNCTION"
>PQescapeBytea</CODE
>
 </DT
><DD
> <CODE
CLASS="FUNCTION"
>PQescapeBytea</CODE
> is an older, deprecated version of
 <CODE
CLASS="FUNCTION"
>PQescapeByteaConn</CODE
>.
<PRE
CLASS="SYNOPSIS"
>unsigned char *PQescapeBytea(const unsigned char *from,
 size_t from_length,
 size_t *to_length);</PRE
>
 The only difference from <CODE
CLASS="FUNCTION"
>PQescapeByteaConn</CODE
> is that
 <CODE
CLASS="FUNCTION"
>PQescapeBytea</CODE
> does not take a <TT
CLASS="STRUCTNAME"
>PGconn</TT
>
 parameter. Because of this, <CODE
CLASS="FUNCTION"
>PQescapeBytea</CODE
> 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 "behind the
 scenes"). It might give the wrong results if
 used in programs that use multiple database connections (use
 <CODE
CLASS="FUNCTION"
>PQescapeByteaConn</CODE
> in such cases).
 </DD
><DT
><A
NAME="LIBPQ-PQUNESCAPEBYTEA"
></A
><CODE
CLASS="FUNCTION"
>PQunescapeBytea</CODE
>
 </DT
><DD
> Converts a string representation of binary data into binary data
 &mdash; the reverse of <CODE
CLASS="FUNCTION"
>PQescapeBytea</CODE
>. This
 is needed when retrieving <TT
CLASS="TYPE"
>bytea</TT
> data in text format,
 but not when retrieving it in binary format.

<PRE
CLASS="SYNOPSIS"
>unsigned char *PQunescapeBytea(const unsigned char *from, size_t *to_length);</PRE
>
 The <TT
CLASS="PARAMETER"
>from</TT
> parameter points to a string
 such as might be returned by <CODE
CLASS="FUNCTION"
>PQgetvalue</CODE
> when applied
 to a <TT
CLASS="TYPE"
>bytea</TT
> column. <CODE
CLASS="FUNCTION"
>PQunescapeBytea</CODE
>
 converts this string representation into its binary representation.
 It returns a pointer to a buffer allocated with
 <CODE
CLASS="FUNCTION"
>malloc()</CODE
>, or <TT
CLASS="SYMBOL"
>NULL</TT
> on error, and puts the size of
 the buffer in <TT
CLASS="PARAMETER"
>to_length</TT
>. The result must be
 freed using <CODE
CLASS="FUNCTION"
>PQfreemem</CODE
> when it is no longer needed.
 This conversion is not exactly the inverse of
 <CODE
CLASS="FUNCTION"
>PQescapeBytea</CODE
>, because the string is not expected
 to be "escaped" when received from <CODE
CLASS="FUNCTION"
>PQgetvalue</CODE
>.
 In particular this means there is no need for string quoting considerations,
 and so no need for a <TT
CLASS="STRUCTNAME"
>PGconn</TT
> parameter.
 </DD
></DL
></DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="libpq-status.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="libpq-async.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Connection Status Functions</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="libpq.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Asynchronous Command Processing</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

FILE FOLDER

Name	Size	Permission
LEGALNOTICE.html	2681 bytes	0644
acronyms.html	16284 bytes	0644
admin.html	12564 bytes	0644
adminpack.html	7889 bytes	0644
app-clusterdb.html	10602 bytes	0644
app-createdb.html	12856 bytes	0644
app-createlang.html	9907 bytes	0644
app-createuser.html	15640 bytes	0644
app-dropdb.html	9642 bytes	0644
app-droplang.html	9638 bytes	0644
app-dropuser.html	9596 bytes	0644
app-ecpg.html	8718 bytes	0644
app-initdb.html	15405 bytes	0644
app-pg-ctl.html	22459 bytes	0644
app-pg-dumpall.html	20706 bytes	0644
app-pgbasebackup.html	19833 bytes	0644
app-pgconfig.html	11093 bytes	0644
app-pgcontroldata.html	3979 bytes	0644
app-pgdump.html	43964 bytes	0644
app-pgreceivexlog.html	11057 bytes	0644
app-pgresetxlog.html	11566 bytes	0644
app-pgrestore.html	30269 bytes	0644
app-postgres.html	31828 bytes	0644
app-postmaster.html	3005 bytes	0644
app-psql.html	138871 bytes	0644
app-reindexdb.html	11281 bytes	0644
app-vacuumdb.html	12616 bytes	0644
appendixes.html	26329 bytes	0644
applevel-consistency.html	10315 bytes	0644
archive-recovery-settings.html	7338 bytes	0644
arrays.html	28079 bytes	0644
auth-delay.html	3780 bytes	0644
auth-methods.html	36202 bytes	0644
auth-pg-hba-conf.html	29759 bytes	0644
auth-username-maps.html	8597 bytes	0644
auto-explain.html	9887 bytes	0644
backup-dump.html	15927 bytes	0644
backup-file.html	7996 bytes	0644
backup.html	4485 bytes	0644
biblio.html	11549 bytes	0644
bki-commands.html	9646 bytes	0644
bki-example.html	3049 bytes	0644
bki-format.html	3463 bytes	0644
bki-structure.html	4320 bytes	0644
bki.html	4330 bytes	0644
bookindex.html	243165 bytes	0644
btree-gin.html	4600 bytes	0644
btree-gist.html	6884 bytes	0644
bug-reporting.html	18646 bytes	0644
catalog-pg-aggregate.html	5502 bytes	0644
catalog-pg-am.html	10547 bytes	0644
catalog-pg-amop.html	7593 bytes	0644
catalog-pg-amproc.html	4885 bytes	0644
catalog-pg-attrdef.html	4364 bytes	0644
catalog-pg-attribute.html	10287 bytes	0644
catalog-pg-auth-members.html	4255 bytes	0644
catalog-pg-authid.html	6815 bytes	0644
catalog-pg-cast.html	6955 bytes	0644
catalog-pg-class.html	12661 bytes	0644
catalog-pg-collation.html	5897 bytes	0644
catalog-pg-constraint.html	11579 bytes	0644
catalog-pg-conversion.html	4430 bytes	0644
catalog-pg-database.html	7027 bytes	0644
catalog-pg-db-role-setting.html	4068 bytes	0644
catalog-pg-default-acl.html	5267 bytes	0644
catalog-pg-depend.html	8635 bytes	0644
catalog-pg-description.html	4478 bytes	0644
catalog-pg-enum.html	4716 bytes	0644
catalog-pg-extension.html	5282 bytes	0644
catalog-pg-foreign-data-wrapper.html	4945 bytes	0644
catalog-pg-foreign-server.html	4688 bytes	0644
catalog-pg-foreign-table.html	4036 bytes	0644
catalog-pg-index.html	8868 bytes	0644
catalog-pg-inherits.html	3888 bytes	0644
catalog-pg-language.html	5952 bytes	0644
catalog-pg-largeobject-metadata.html	3630 bytes	0644
catalog-pg-largeobject.html	5154 bytes	0644
catalog-pg-namespace.html	3751 bytes	0644
catalog-pg-opclass.html	5863 bytes	0644
catalog-pg-operator.html	6645 bytes	0644
catalog-pg-opfamily.html	4811 bytes	0644
catalog-pg-pltemplate.html	5364 bytes	0644
catalog-pg-proc.html	13403 bytes	0644
catalog-pg-range.html	5182 bytes	0644
catalog-pg-rewrite.html	5391 bytes	0644
catalog-pg-seclabel.html	4515 bytes	0644
catalog-pg-shdepend.html	7043 bytes	0644
catalog-pg-shdescription.html	4247 bytes	0644
catalog-pg-shseclabel.html	4404 bytes	0644
catalog-pg-statistic.html	9538 bytes	0644
catalog-pg-tablespace.html	4158 bytes	0644
catalog-pg-trigger.html	8287 bytes	0644
catalog-pg-ts-config-map.html	4193 bytes	0644
catalog-pg-ts-config.html	4481 bytes	0644
catalog-pg-ts-dict.html	4716 bytes	0644
catalog-pg-ts-parser.html	5082 bytes	0644
catalog-pg-ts-template.html	4258 bytes	0644
catalog-pg-type.html	19905 bytes	0644
catalog-pg-user-mapping.html	3847 bytes	0644
catalogs-overview.html	10431 bytes	0644
catalogs.html	10387 bytes	0644
charset.html	4162 bytes	0644
chkpass.html	4391 bytes	0644
citext.html	11148 bytes	0644
client-authentication-problems.html	4224 bytes	0644
client-authentication.html	5914 bytes	0644
client-interfaces.html	13717 bytes	0644
collation.html	14222 bytes	0644
config-setting.html	11146 bytes	0644
connect-estab.html	4315 bytes	0644
continuous-archiving.html	49830 bytes	0644
contrib-dblink-build-sql-delete.html	5451 bytes	0644
contrib-dblink-build-sql-insert.html	6052 bytes	0644
contrib-dblink-build-sql-update.html	6281 bytes	0644
contrib-dblink-cancel-query.html	3820 bytes	0644
contrib-dblink-close.html	4650 bytes	0644
contrib-dblink-connect-u.html	4482 bytes	0644
contrib-dblink-connect.html	7325 bytes	0644
contrib-dblink-disconnect.html	3718 bytes	0644
contrib-dblink-error-message.html	3508 bytes	0644
contrib-dblink-exec.html	5466 bytes	0644
contrib-dblink-fetch.html	5979 bytes	0644
contrib-dblink-function.html	8630 bytes	0644
contrib-dblink-get-connections.html	3206 bytes	0644
contrib-dblink-get-notify.html	4168 bytes	0644
contrib-dblink-get-pkey.html	4498 bytes	0644
contrib-dblink-get-result.html	6959 bytes	0644
contrib-dblink-is-busy.html	3490 bytes	0644
contrib-dblink-open.html	5464 bytes	0644
contrib-dblink-send-query.html	4170 bytes	0644
contrib-prog-client.html	3434 bytes	0644
contrib-prog-server.html	3837 bytes	0644
contrib-prog.html	3320 bytes	0644
contrib-spi.html	11236 bytes	0644
contrib.html	8904 bytes	0644
creating-cluster.html	12465 bytes	0644
cube.html	15941 bytes	0644
database-roles.html	6092 bytes	0644
datatype-binary.html	12893 bytes	0644
datatype-bit.html	5096 bytes	0644
datatype-boolean.html	5267 bytes	0644
datatype-character.html	11893 bytes	0644
datatype-datetime.html	50763 bytes	0644
datatype-enum.html	6433 bytes	0644
datatype-geometric.html	12503 bytes	0644
datatype-json.html	3439 bytes	0644
datatype-money.html	5482 bytes	0644
datatype-net-types.html	10423 bytes	0644
datatype-numeric.html	22353 bytes	0644
datatype-oid.html	9686 bytes	0644
datatype-pseudo.html	7285 bytes	0644
datatype-textsearch.html	10033 bytes	0644
datatype-uuid.html	4560 bytes	0644
datatype-xml.html	11334 bytes	0644
datatype.html	16609 bytes	0644
datetime-appendix.html	3525 bytes	0644
datetime-config-files.html	8980 bytes	0644
datetime-input-rules.html	6763 bytes	0644
datetime-keywords.html	5096 bytes	0644
datetime-units-history.html	7634 bytes	0644
dblink.html	5322 bytes	0644
ddl-alter.html	10498 bytes	0644
ddl-basics.html	7816 bytes	0644
ddl-constraints.html	22790 bytes	0644
ddl-default.html	4540 bytes	0644
ddl-depend.html	6498 bytes	0644
ddl-foreign-data.html	4485 bytes	0644
ddl-inherit.html	15308 bytes	0644
ddl-others.html	3080 bytes	0644
ddl-partitioning.html	27763 bytes	0644
ddl-priv.html	6066 bytes	0644
ddl-schemas.html	18046 bytes	0644
ddl-system-columns.html	8049 bytes	0644
ddl.html	6382 bytes	0644
dict-int.html	4793 bytes	0644
dict-xsyn.html	6481 bytes	0644
different-replication-solutions.html	14793 bytes	0644
disk-full.html	3517 bytes	0644
disk-usage.html	5661 bytes	0644
diskusage.html	2668 bytes	0644
dml-delete.html	3565 bytes	0644
dml-insert.html	5801 bytes	0644
dml-returning.html	5104 bytes	0644
dml-update.html	5556 bytes	0644
dml.html	2944 bytes	0644
docguide-authoring.html	6757 bytes	0644
docguide-build.html	15280 bytes	0644
docguide-docbook.html	3853 bytes	0644
docguide-style.html	7429 bytes	0644
docguide-toolsets.html	20683 bytes	0644
docguide.html	3624 bytes	0644
dummy-seclabel.html	4358 bytes	0644
dynamic-trace.html	27234 bytes	0644
earthdistance.html	8806 bytes	0644
ecpg-commands.html	9527 bytes	0644
ecpg-concept.html	4979 bytes	0644
ecpg-connect.html	10826 bytes	0644
ecpg-cpp.html	9624 bytes	0644
ecpg-descriptors.html	34909 bytes	0644
ecpg-develop.html	7964 bytes	0644
ecpg-dynamic.html	6515 bytes	0644
ecpg-errors.html	25737 bytes	0644
ecpg-informix-compat.html	52760 bytes	0644
ecpg-library.html	5798 bytes	0644
ecpg-lo.html	5527 bytes	0644
ecpg-pgtypes.html	54457 bytes	0644
ecpg-preproc.html	8985 bytes	0644
ecpg-process.html	5386 bytes	0644
ecpg-sql-allocate-descriptor.html	3983 bytes	0644
ecpg-sql-commands.html	4698 bytes	0644
ecpg-sql-connect.html	9375 bytes	0644
ecpg-sql-deallocate-descriptor.html	3773 bytes	0644
ecpg-sql-declare.html	5397 bytes	0644
ecpg-sql-describe.html	4595 bytes	0644
ecpg-sql-disconnect.html	4733 bytes	0644
ecpg-sql-execute-immediate.html	3877 bytes	0644
ecpg-sql-get-descriptor.html	7709 bytes	0644
ecpg-sql-open.html	4642 bytes	0644
ecpg-sql-prepare.html	4177 bytes	0644
ecpg-sql-set-autocommit.html	3333 bytes	0644
ecpg-sql-set-connection.html	3929 bytes	0644
ecpg-sql-set-descriptor.html	5505 bytes	0644
ecpg-sql-type.html	5026 bytes	0644
ecpg-sql-var.html	3539 bytes	0644
ecpg-sql-whenever.html	4686 bytes	0644
ecpg-variables.html	40283 bytes	0644
ecpg.html	10344 bytes	0644
encryption-options.html	7495 bytes	0644
errcodes-appendix.html	36965 bytes	0644
error-message-reporting.html	14124 bytes	0644
error-style-guide.html	16769 bytes	0644
event-log-registration.html	4188 bytes	0644
executor.html	6612 bytes	0644
explicit-joins.html	11019 bytes	0644
explicit-locking.html	25073 bytes	0644
extend-extensions.html	32430 bytes	0644
extend-how.html	4552 bytes	0644
extend-pgxs.html	11761 bytes	0644
extend-type-system.html	10111 bytes	0644
extend.html	9982 bytes	0644
external-admin-tools.html	2722 bytes	0644
external-extensions.html	3263 bytes	0644
external-interfaces.html	5513 bytes	0644
external-pl.html	4670 bytes	0644
external-projects.html	3004 bytes	0644
fdw-callbacks.html	12905 bytes	0644
fdw-functions.html	4496 bytes	0644
fdw-helpers.html	5988 bytes	0644
fdw-planning.html	9845 bytes	0644
fdwhandler.html	3990 bytes	0644
features-sql-standard.html	39105 bytes	0644
features.html	7566 bytes	0644
file-fdw.html	7709 bytes	0644
functions-admin.html	50395 bytes	0644
functions-aggregate.html	21814 bytes	0644
functions-array.html	13521 bytes	0644
functions-binarystring.html	12588 bytes	0644
functions-bitstring.html	6786 bytes	0644
functions-comparison.html	10638 bytes	0644
functions-comparisons.html	13531 bytes	0644
functions-conditional.html	11007 bytes	0644
functions-datetime.html	48303 bytes	0644
functions-enum.html	5491 bytes	0644
functions-formatting.html	35401 bytes	0644
functions-geometry.html	20347 bytes	0644
functions-info.html	58658 bytes	0644
functions-json.html	3814 bytes	0644
functions-logical.html	4665 bytes	0644
functions-matching.html	75728 bytes	0644
functions-math.html	20401 bytes	0644
functions-net.html	13502 bytes	0644
functions-range.html	10857 bytes	0644
functions-sequence.html	12925 bytes	0644
functions-srf.html	8840 bytes	0644
functions-string.html	59052 bytes	0644
functions-subquery.html	16381 bytes	0644
functions-textsearch.html	20488 bytes	0644
functions-trigger.html	4548 bytes	0644
functions-window.html	12085 bytes	0644
functions-xml.html	32169 bytes	0644
functions.html	9939 bytes	0644
fuzzystrmatch.html	8061 bytes	0644
geqo-biblio.html	3459 bytes	0644
geqo-intro.html	4415 bytes	0644
geqo-intro2.html	5627 bytes	0644
geqo-pg-intro.html	8785 bytes	0644
geqo.html	3616 bytes	0644
gin-examples.html	3322 bytes	0644
gin-extensibility.html	14402 bytes	0644
gin-implementation.html	6564 bytes	0644
gin-intro.html	4662 bytes	0644
gin-limit.html	2817 bytes	0644
gin-tips.html	5713 bytes	0644
gin.html	2929 bytes	0644
gist-examples.html	3752 bytes	0644
gist-extensibility.html	24354 bytes	0644
gist-implementation.html	4101 bytes	0644
gist-intro.html	3616 bytes	0644
gist.html	2679 bytes	0644
git.html	4564 bytes	0644
high-availability.html	7698 bytes	0644
history.html	11918 bytes	0644
hot-standby.html	36045 bytes	0644
hstore.html	22629 bytes	0644
index-catalog.html	7996 bytes	0644
index-cost-estimation.html	9991 bytes	0644
index-functions.html	19114 bytes	0644
index-locking.html	8049 bytes	0644
index-scanning.html	10707 bytes	0644
index-unique-checks.html	9192 bytes	0644
index.html	8071 bytes	0644
indexam.html	5247 bytes	0644
indexes-bitmap-scans.html	6580 bytes	0644
indexes-collations.html	3640 bytes	0644
indexes-examine.html	7161 bytes	0644
indexes-expressional.html	4813 bytes	0644
indexes-intro.html	6313 bytes	0644
indexes-multicolumn.html	6298 bytes	0644
indexes-opclass.html	7336 bytes	0644
indexes-ordering.html	6480 bytes	0644
indexes-partial.html	11812 bytes	0644
indexes-types.html	10233 bytes	0644
indexes-unique.html	4002 bytes	0644
indexes.html	3619 bytes	0644
information-schema.html	11177 bytes	0644
infoschema-administrable-role-authorizations.html	3751 bytes	0644
infoschema-applicable-roles.html	3970 bytes	0644
infoschema-attributes.html	12807 bytes	0644
infoschema-character-sets.html	7050 bytes	0644
infoschema-check-constraint-routine-usage.html	4349 bytes	0644
infoschema-check-constraints.html	3876 bytes	0644
infoschema-collation-character-set-applicab.html	4425 bytes	0644
infoschema-collations.html	3885 bytes	0644
infoschema-column-domain-usage.html	4322 bytes	0644
infoschema-column-options.html	4109 bytes	0644
infoschema-column-privileges.html	5029 bytes	0644
infoschema-column-udt-usage.html	4583 bytes	0644
infoschema-columns.html	17625 bytes	0644
infoschema-constraint-column-usage.html	4873 bytes	0644
infoschema-constraint-table-usage.html	4774 bytes	0644
infoschema-data-type-privileges.html	5089 bytes	0644
infoschema-datatypes.html	4229 bytes	0644
infoschema-domain-constraints.html	4664 bytes	0644
infoschema-domain-udt-usage.html	4171 bytes	0644
infoschema-domains.html	11367 bytes	0644
infoschema-element-types.html	11374 bytes	0644
infoschema-enabled-roles.html	3780 bytes	0644
infoschema-foreign-data-wrapper-options.html	3910 bytes	0644
infoschema-foreign-data-wrappers.html	4227 bytes	0644
infoschema-foreign-server-options.html	3853 bytes	0644
infoschema-foreign-servers.html	4571 bytes	0644
infoschema-foreign-table-options.html	3974 bytes	0644
infoschema-foreign-tables.html	4072 bytes	0644
infoschema-information-schema-catalog-name.html	3357 bytes	0644
infoschema-key-column-usage.html	5185 bytes	0644
infoschema-parameters.html	10799 bytes	0644
infoschema-referential-constraints.html	5664 bytes	0644
infoschema-role-column-grants.html	5017 bytes	0644
infoschema-role-routine-grants.html	5360 bytes	0644
infoschema-role-table-grants.html	5427 bytes	0644
infoschema-role-udt-grants.html	4781 bytes	0644
infoschema-role-usage-grants.html	5010 bytes	0644
infoschema-routine-privileges.html	5032 bytes	0644
infoschema-routines.html	23052 bytes	0644
infoschema-schema.html	3180 bytes	0644
infoschema-schemata.html	4248 bytes	0644
infoschema-sequences.html	6111 bytes	0644
infoschema-sql-features.html	4708 bytes	0644
infoschema-sql-implementation-info.html	4503 bytes	0644
infoschema-sql-languages.html	5094 bytes	0644
infoschema-sql-packages.html	4178 bytes	0644
infoschema-sql-parts.html	4080 bytes	0644
infoschema-sql-sizing-profiles.html	4177 bytes	0644
infoschema-sql-sizing.html	4101 bytes	0644
infoschema-table-constraints.html	4914 bytes	0644
infoschema-table-privileges.html	5097 bytes	0644
infoschema-tables.html	5957 bytes	0644
infoschema-triggered-update-columns.html	4554 bytes	0644
infoschema-triggers.html	9447 bytes	0644
infoschema-udt-privileges.html	4509 bytes	0644
infoschema-usage-privileges.html	5512 bytes	0644
infoschema-user-defined-types.html	9753 bytes	0644
infoschema-user-mapping-options.html	4449 bytes	0644
infoschema-user-mappings.html	3833 bytes	0644
infoschema-view-column-usage.html	4728 bytes	0644
infoschema-view-routine-usage.html	4368 bytes	0644
infoschema-view-table-usage.html	4389 bytes	0644
infoschema-views.html	5529 bytes	0644
install-getsource.html	3574 bytes	0644
install-post.html	8076 bytes	0644
install-procedure.html	46527 bytes	0644
install-requirements.html	14481 bytes	0644
install-short.html	2870 bytes	0644
install-windows-full.html	19274 bytes	0644
install-windows-libpq.html	6283 bytes	0644
install-windows.html	6620 bytes	0644
installation-platform-notes.html	39380 bytes	0644
installation.html	4160 bytes	0644
intagg.html	6254 bytes	0644
intarray.html	13757 bytes	0644
internals.html	15638 bytes	0644
intro-whatis.html	4011 bytes	0644
isn.html	13356 bytes	0644
kernel-resources.html	37822 bytes	0644
largeobjects.html	4675 bytes	0644
libpq-async.html	21020 bytes	0644
libpq-build.html	6369 bytes	0644
libpq-cancel.html	6777 bytes	0644
libpq-connect.html	51248 bytes	0644
libpq-control.html	6280 bytes	0644
libpq-copy.html	22442 bytes	0644
libpq-envars.html	9820 bytes	0644
libpq-events.html	23093 bytes	0644
libpq-example.html	16024 bytes	0644
libpq-exec.html	64877 bytes	0644
libpq-fastpath.html	6124 bytes	0644
libpq-ldap.html	5506 bytes	0644
libpq-misc.html	13815 bytes	0644
libpq-notice-processing.html	6284 bytes	0644
libpq-notify.html	6715 bytes	0644
libpq-pgpass.html	4861 bytes	0644
libpq-pgservice.html	3905 bytes	0644
libpq-single-row-mode.html	6353 bytes	0644
libpq-ssl.html	19972 bytes	0644
libpq-status.html	17695 bytes	0644
libpq-threading.html	5544 bytes	0644
libpq.html	7918 bytes	0644
lo-examplesect.html	8696 bytes	0644
lo-funcs.html	4640 bytes	0644
lo-implementation.html	3353 bytes	0644
lo-interfaces.html	15155 bytes	0644
lo-intro.html	3206 bytes	0644
lo.html	6627 bytes	0644
locale.html	13691 bytes	0644
locking-indexes.html	4350 bytes	0644
log-shipping-alternative.html	11057 bytes	0644
logfile-maintenance.html	7143 bytes	0644
ltree.html	27295 bytes	0644
maintenance.html	5538 bytes	0644
manage-ag-config.html	3746 bytes	0644
manage-ag-createdb.html	6310 bytes	0644
manage-ag-dropdb.html	3605 bytes	0644
manage-ag-overview.html	5144 bytes	0644
manage-ag-tablespaces.html	9250 bytes	0644
manage-ag-templatedbs.html	8162 bytes	0644
managing-databases.html	3273 bytes	0644
monitoring-locks.html	3673 bytes	0644
monitoring-ps.html	6782 bytes	0644
monitoring-stats.html	58063 bytes	0644
monitoring.html	4458 bytes	0644
multibyte.html	31965 bytes	0644
mvcc-caveats.html	4077 bytes	0644
mvcc-intro.html	4552 bytes	0644
mvcc.html	4302 bytes	0644
nls-programmer.html	10078 bytes	0644
nls-translator.html	14522 bytes	0644
nls.html	3134 bytes	0644
non-durability.html	4484 bytes	0644
notation.html	4415 bytes	0644
oid2name.html	11962 bytes	0644
overview.html	4093 bytes	0644
pageinspect.html	8117 bytes	0644
parser-stage.html	8117 bytes	0644
passwordcheck.html	4788 bytes	0644
performance-tips.html	4501 bytes	0644
perm-functions.html	3338 bytes	0644
pgarchivecleanup.html	8999 bytes	0644
pgbench.html	30833 bytes	0644
pgbuffercache.html	7715 bytes	0644
pgcrypto.html	38804 bytes	0644
pgfreespacemap.html	5230 bytes	0644
pgrowlocks.html	6078 bytes	0644
pgstandby.html	15204 bytes	0644
pgstatstatements.html	16068 bytes	0644
pgstattuple.html	9449 bytes	0644
pgtestfsync.html	5254 bytes	0644
pgtesttiming.html	12476 bytes	0644
pgtrgm.html	12333 bytes	0644
pgupgrade.html	24737 bytes	0644
planner-optimizer.html	9396 bytes	0644
planner-stats-details.html	3276 bytes	0644
planner-stats-security.html	5556 bytes	0644
planner-stats.html	9058 bytes	0644
plhandler.html	13748 bytes	0644
plperl-builtins.html	18276 bytes	0644
plperl-data.html	2878 bytes	0644
plperl-funcs.html	13369 bytes	0644
plperl-global.html	5067 bytes	0644
plperl-triggers.html	6446 bytes	0644
plperl-trusted.html	6712 bytes	0644
plperl-under-the-hood.html	8991 bytes	0644
plperl.html	4930 bytes	0644
plpgsql-control-structures.html	46183 bytes	0644
plpgsql-cursors.html	25586 bytes	0644
plpgsql-declarations.html	21746 bytes	0644
plpgsql-development-tips.html	9511 bytes	0644
plpgsql-errors-and-messages.html	10094 bytes	0644
plpgsql-expressions.html	4662 bytes	0644
plpgsql-implementation.html	18043 bytes	0644
plpgsql-overview.html	9032 bytes	0644
plpgsql-porting.html	27094 bytes	0644
plpgsql-statements.html	32221 bytes	0644
plpgsql-structure.html	8329 bytes	0644
plpgsql-trigger.html	22322 bytes	0644
plpgsql.html	6965 bytes	0644
plpython-data.html	14648 bytes	0644
plpython-database.html	15413 bytes	0644
plpython-do.html	2771 bytes	0644
plpython-envar.html	3885 bytes	0644
plpython-funcs.html	5478 bytes	0644
plpython-python23.html	7207 bytes	0644
plpython-sharing.html	3032 bytes	0644
plpython-subtransaction.html	7888 bytes	0644
plpython-trigger.html	5069 bytes	0644
plpython-util.html	5104 bytes	0644
plpython.html	6067 bytes	0644
pltcl-data.html	2906 bytes	0644
pltcl-dbaccess.html	13902 bytes	0644
pltcl-functions.html	6177 bytes	0644
pltcl-global.html	5066 bytes	0644
pltcl-overview.html	5288 bytes	0644
pltcl-procnames.html	3222 bytes	0644
pltcl-trigger.html	9452 bytes	0644
pltcl-unknown.html	5075 bytes	0644
pltcl.html	3400 bytes	0644
populate.html	17114 bytes	0644
postgres-user.html	3314 bytes	0644
preface.html	5070 bytes	0644
preventing-server-spoofing.html	4604 bytes	0644
protocol-changes.html	6650 bytes	0644
protocol-error-fields.html	6131 bytes	0644
protocol-flow.html	46202 bytes	0644
protocol-message-formats.html	40844 bytes	0644
protocol-message-types.html	4933 bytes	0644
protocol-overview.html	9670 bytes	0644
protocol-replication.html	14666 bytes	0644
protocol.html	5652 bytes	0644
queries-limit.html	5335 bytes	0644
queries-order.html	7369 bytes	0644
queries-overview.html	5068 bytes	0644
queries-select-lists.html	9308 bytes	0644
queries-table-expressions.html	39874 bytes	0644
queries-union.html	5114 bytes	0644
queries-values.html	4930 bytes	0644
queries-with.html	20880 bytes	0644
queries.html	4418 bytes	0644
query-path.html	5470 bytes	0644
querytree.html	11136 bytes	0644
rangetypes.html	22735 bytes	0644
recovery-config.html	3550 bytes	0644
recovery-target-settings.html	7762 bytes	0644
reference-client.html	6102 bytes	0644
reference-server.html	3964 bytes	0644
reference.html	23162 bytes	0644
regress-coverage.html	3325 bytes	0644
regress-evaluation.html	12487 bytes	0644
regress-run.html	13710 bytes	0644
regress-variant.html	7177 bytes	0644
regress.html	4277 bytes	0644
release-0-01.html	2555 bytes	0644
release-0-02.html	4292 bytes	0644
release-0-03.html	7798 bytes	0644
release-1-0.html	4229 bytes	0644
release-1-01.html	9346 bytes	0644
release-1-02.html	6489 bytes	0644
release-1-09.html	2525 bytes	0644
release-6-0.html	7920 bytes	0644
release-6-1-1.html	3719 bytes	0644
release-6-1.html	9025 bytes	0644
release-6-2-1.html	4405 bytes	0644
release-6-2.html	8883 bytes	0644
release-6-3-1.html	4444 bytes	0644
release-6-3-2.html	4157 bytes	0644
release-6-3.html	16311 bytes	0644
release-6-4-1.html	4061 bytes	0644
release-6-4-2.html	2908 bytes	0644
release-6-4.html	14732 bytes	0644
release-6-5-1.html	3842 bytes	0644
release-6-5-2.html	4102 bytes	0644
release-6-5-3.html	3053 bytes	0644
release-6-5.html	17387 bytes	0644
release-7-0-1.html	3920 bytes	0644
release-7-0-2.html	2887 bytes	0644
release-7-0-3.html	4656 bytes	0644
release-7-0.html	23104 bytes	0644
release-7-1-1.html	3262 bytes	0644
release-7-1-2.html	2975 bytes	0644
release-7-1-3.html	3139 bytes	0644
release-7-1.html	13017 bytes	0644
release-7-2-1.html	4011 bytes	0644
release-7-2-2.html	3793 bytes	0644
release-7-2-3.html	3364 bytes	0644
release-7-2-4.html	3587 bytes	0644
release-7-2-5.html	3746 bytes	0644
release-7-2-6.html	3624 bytes	0644
release-7-2-7.html	3726 bytes	0644
release-7-2-8.html	3948 bytes	0644
release-7-2.html	27098 bytes	0644
release-7-3-1.html	4168 bytes	0644
release-7-3-10.html	7493 bytes	0644
release-7-3-11.html	4111 bytes	0644
release-7-3-12.html	3527 bytes	0644
release-7-3-13.html	4618 bytes	0644
release-7-3-14.html	3931 bytes	0644
release-7-3-15.html	6315 bytes	0644
release-7-3-16.html	3424 bytes	0644
release-7-3-17.html	3550 bytes	0644
release-7-3-18.html	3647 bytes	0644
release-7-3-19.html	3686 bytes	0644
release-7-3-2.html	5205 bytes	0644
release-7-3-20.html	3524 bytes	0644
release-7-3-21.html	6216 bytes	0644
release-7-3-3.html	10290 bytes	0644
release-7-3-4.html	3502 bytes	0644
release-7-3-5.html	4493 bytes	0644
release-7-3-6.html	4428 bytes	0644
release-7-3-7.html	3352 bytes	0644
release-7-3-8.html	3571 bytes	0644
release-7-3-9.html	4079 bytes	0644
release-7-3.html	33053 bytes	0644
release-7-4-1.html	7116 bytes	0644
release-7-4-10.html	3806 bytes	0644
release-7-4-11.html	4857 bytes	0644
release-7-4-12.html	4221 bytes	0644
release-7-4-13.html	6961 bytes	0644
release-7-4-14.html	3673 bytes	0644
release-7-4-15.html	4270 bytes	0644
release-7-4-16.html	3972 bytes	0644
release-7-4-17.html	4013 bytes	0644
release-7-4-18.html	3927 bytes	0644
release-7-4-19.html	7242 bytes	0644
release-7-4-2.html	8260 bytes	0644
release-7-4-20.html	6605 bytes	0644
release-7-4-21.html	3922 bytes	0644
release-7-4-22.html	4071 bytes	0644
release-7-4-23.html	4423 bytes	0644
release-7-4-24.html	4289 bytes	0644
release-7-4-25.html	4506 bytes	0644
release-7-4-26.html	5455 bytes	0644
release-7-4-27.html	5164 bytes	0644
release-7-4-28.html	5629 bytes	0644
release-7-4-29.html	6960 bytes	0644
release-7-4-3.html	4615 bytes	0644
release-7-4-30.html	6211 bytes	0644
release-7-4-4.html	4085 bytes	0644
release-7-4-5.html	3194 bytes	0644
release-7-4-6.html	4731 bytes	0644
release-7-4-7.html	4274 bytes	0644
release-7-4-8.html	10156 bytes	0644
release-7-4-9.html	5118 bytes	0644
release-7-4.html	57378 bytes	0644
release-8-0-1.html	4744 bytes	0644
release-8-0-10.html	4751 bytes	0644
release-8-0-11.html	3969 bytes	0644
release-8-0-12.html	3134 bytes	0644
release-8-0-13.html	4118 bytes	0644
release-8-0-14.html	4518 bytes	0644
release-8-0-15.html	9101 bytes	0644
release-8-0-16.html	8946 bytes	0644
release-8-0-17.html	3920 bytes	0644
release-8-0-18.html	5579 bytes	0644
release-8-0-19.html	4976 bytes	0644
release-8-0-2.html	9566 bytes	0644
release-8-0-20.html	4312 bytes	0644
release-8-0-21.html	4504 bytes	0644
release-8-0-22.html	6440 bytes	0644
release-8-0-23.html	6023 bytes	0644
release-8-0-24.html	7002 bytes	0644
release-8-0-25.html	7427 bytes	0644
release-8-0-26.html	8026 bytes	0644
release-8-0-3.html	7425 bytes	0644
release-8-0-4.html	6680 bytes	0644
release-8-0-5.html	4816 bytes	0644
release-8-0-6.html	5694 bytes	0644
release-8-0-7.html	5909 bytes	0644
release-8-0-8.html	7225 bytes	0644
release-8-0-9.html	4306 bytes	0644
release-8-0.html	66818 bytes	0644
release-8-1-1.html	5459 bytes	0644
release-8-1-10.html	4781 bytes	0644
release-8-1-11.html	9946 bytes	0644
release-8-1-12.html	9341 bytes	0644
release-8-1-13.html	4292 bytes	0644
release-8-1-14.html	6901 bytes	0644
release-8-1-15.html	6274 bytes	0644
release-8-1-16.html	5278 bytes	0644
release-8-1-17.html	6035 bytes	0644
release-8-1-18.html	6442 bytes	0644
release-8-1-19.html	6612 bytes	0644
release-8-1-2.html	6335 bytes	0644
release-8-1-20.html	7298 bytes	0644
release-8-1-21.html	7213 bytes	0644
release-8-1-22.html	8324 bytes	0644
release-8-1-23.html	7933 bytes	0644
release-8-1-3.html	7026 bytes	0644
release-8-1-4.html	8873 bytes	0644
release-8-1-5.html	5479 bytes	0644
release-8-1-6.html	5337 bytes	0644
release-8-1-7.html	4558 bytes	0644
release-8-1-8.html	3116 bytes	0644
release-8-1-9.html	4388 bytes	0644
release-8-1.html	62113 bytes	0644
release-8-2-1.html	5065 bytes	0644
release-8-2-10.html	8180 bytes	0644
release-8-2-11.html	7147 bytes	0644
release-8-2-12.html	6748 bytes	0644
release-8-2-13.html	7348 bytes	0644
release-8-2-14.html	7876 bytes	0644
release-8-2-15.html	8155 bytes	0644
release-8-2-16.html	9293 bytes	0644
release-8-2-17.html	8214 bytes	0644
release-8-2-18.html	10277 bytes	0644
release-8-2-19.html	8589 bytes	0644
release-8-2-2.html	5802 bytes	0644
release-8-2-20.html	6244 bytes	0644
release-8-2-21.html	5593 bytes	0644
release-8-2-22.html	9617 bytes	0644
release-8-2-23.html	9559 bytes	0644
release-8-2-3.html	3095 bytes	0644
release-8-2-4.html	5428 bytes	0644
release-8-2-5.html	5995 bytes	0644
release-8-2-6.html	10551 bytes	0644
release-8-2-7.html	9311 bytes	0644
release-8-2-8.html	7521 bytes	0644
release-8-2-9.html	4281 bytes	0644
release-8-2.html	69398 bytes	0644
release-8-3-1.html	10585 bytes	0644
release-8-3-10.html	10725 bytes	0644
release-8-3-11.html	8963 bytes	0644
release-8-3-12.html	12119 bytes	0644
release-8-3-13.html	9506 bytes	0644
release-8-3-14.html	6242 bytes	0644
release-8-3-15.html	6381 bytes	0644
release-8-3-16.html	11015 bytes	0644
release-8-3-17.html	10590 bytes	0644
release-8-3-18.html	11265 bytes	0644
release-8-3-19.html	8466 bytes	0644
release-8-3-2.html	12203 bytes	0644
release-8-3-20.html	9251 bytes	0644
release-8-3-21.html	5034 bytes	0644
release-8-3-22.html	10585 bytes	0644
release-8-3-23.html	6284 bytes	0644
release-8-3-3.html	4275 bytes	0644
release-8-3-4.html	11273 bytes	0644
release-8-3-5.html	8689 bytes	0644
release-8-3-6.html	9197 bytes	0644
release-8-3-7.html	9729 bytes	0644
release-8-3-8.html	9260 bytes	0644
release-8-3-9.html	10206 bytes	0644
release-8-3.html	69773 bytes	0644
release-8-4-1.html	9563 bytes	0644
release-8-4-10.html	11932 bytes	0644
release-8-4-11.html	13787 bytes	0644
release-8-4-12.html	9987 bytes	0644
release-8-4-13.html	9714 bytes	0644
release-8-4-14.html	5117 bytes	0644
release-8-4-15.html	10626 bytes	0644
release-8-4-16.html	7329 bytes	0644
release-8-4-17.html	9572 bytes	0644
release-8-4-18.html	7048 bytes	0644
release-8-4-19.html	7780 bytes	0644
release-8-4-2.html	15697 bytes	0644
release-8-4-20.html	16258 bytes	0644
release-8-4-21.html	5450 bytes	0644
release-8-4-22.html	11306 bytes	0644
release-8-4-3.html	13928 bytes	0644
release-8-4-4.html	10736 bytes	0644
release-8-4-5.html	15933 bytes	0644
release-8-4-6.html	10430 bytes	0644
release-8-4-7.html	6220 bytes	0644
release-8-4-8.html	8850 bytes	0644
release-8-4-9.html	14528 bytes	0644
release-8-4.html	87976 bytes	0644
release-9-0-1.html	5946 bytes	0644
release-9-0-10.html	5693 bytes	0644
release-9-0-11.html	12666 bytes	0644
release-9-0-12.html	8824 bytes	0644
release-9-0-13.html	11671 bytes	0644
release-9-0-14.html	8759 bytes	0644
release-9-0-15.html	9147 bytes	0644
release-9-0-16.html	17408 bytes	0644
release-9-0-17.html	6335 bytes	0644
release-9-0-18.html	11879 bytes	0644
release-9-0-19.html	26610 bytes	0644
release-9-0-2.html	13636 bytes	0644
release-9-0-20.html	15836 bytes	0644
release-9-0-21.html	5166 bytes	0644
release-9-0-22.html	4321 bytes	0644
release-9-0-23.html	16158 bytes	0644
release-9-0-3.html	7256 bytes	0644
release-9-0-4.html	11345 bytes	0644
release-9-0-5.html	17915 bytes	0644
release-9-0-6.html	13426 bytes	0644
release-9-0-7.html	18091 bytes	0644
release-9-0-8.html	10993 bytes	0644
release-9-0-9.html	11743 bytes	0644
release-9-0.html	96127 bytes	0644
release-9-1-1.html	3670 bytes	0644
release-9-1-10.html	10352 bytes	0644
release-9-1-11.html	9584 bytes	0644
release-9-1-12.html	18554 bytes	0644
release-9-1-13.html	6685 bytes	0644
release-9-1-14.html	13036 bytes	0644
release-9-1-15.html	28969 bytes	0644
release-9-1-16.html	19119 bytes	0644
release-9-1-17.html	4947 bytes	0644
release-9-1-18.html	4102 bytes	0644
release-9-1-19.html	17617 bytes	0644
release-9-1-2.html	21571 bytes	0644
release-9-1-20.html	17541 bytes	0644
release-9-1-21.html	7601 bytes	0644
release-9-1-22.html	7258 bytes	0644
release-9-1-23.html	12653 bytes	0644
release-9-1-24.html	8731 bytes	0644
release-9-1-3.html	21153 bytes	0644
release-9-1-4.html	16018 bytes	0644
release-9-1-5.html	14042 bytes	0644
release-9-1-6.html	9521 bytes	0644
release-9-1-7.html	14941 bytes	0644
release-9-1-8.html	10154 bytes	0644
release-9-1-9.html	12679 bytes	0644
release-9-1.html	78963 bytes	0644
release-9-2-1.html	7111 bytes	0644
release-9-2-10.html	32368 bytes	0644
release-9-2-11.html	20298 bytes	0644
release-9-2-12.html	5130 bytes	0644
release-9-2-13.html	4102 bytes	0644
release-9-2-14.html	18386 bytes	0644
release-9-2-15.html	18605 bytes	0644
release-9-2-16.html	7598 bytes	0644
release-9-2-17.html	8195 bytes	0644
release-9-2-18.html	12718 bytes	0644
release-9-2-19.html	10514 bytes	0644
release-9-2-2.html	23001 bytes	0644
release-9-2-20.html	13332 bytes	0644
release-9-2-21.html	14198 bytes	0644
release-9-2-22.html	15865 bytes	0644
release-9-2-23.html	8126 bytes	0644
release-9-2-24.html	7877 bytes	0644
release-9-2-3.html	13373 bytes	0644
release-9-2-4.html	14800 bytes	0644
release-9-2-5.html	12005 bytes	0644
release-9-2-6.html	11684 bytes	0644
release-9-2-7.html	20022 bytes	0644
release-9-2-8.html	7375 bytes	0644
release-9-2-9.html	15615 bytes	0644
release-9-2.html	79519 bytes	0644
release.html	22882 bytes	0644
resources.html	4226 bytes	0644
role-attributes.html	7855 bytes	0644
role-membership.html	8390 bytes	0644
role-removal.html	5303 bytes	0644
routine-reindex.html	3628 bytes	0644
routine-vacuuming.html	38023 bytes	0644
row-estimation-examples.html	20767 bytes	0644
rowtypes.html	23412 bytes	0644
rule-system.html	4117 bytes	0644
rules-privileges.html	11663 bytes	0644
rules-status.html	4512 bytes	0644
rules-triggers.html	9476 bytes	0644
rules-update.html	32615 bytes	0644
rules-views.html	26888 bytes	0644
rules.html	4948 bytes	0644
runtime-config-autovacuum.html	10974 bytes	0644
runtime-config-client.html	32815 bytes	0644
runtime-config-compatible.html	14827 bytes	0644
runtime-config-connection.html	23478 bytes	0644
runtime-config-custom.html	3548 bytes	0644
runtime-config-developer.html	14070 bytes	0644
runtime-config-error-handling.html	3570 bytes	0644
runtime-config-file-locations.html	6977 bytes	0644
runtime-config-locks.html	7634 bytes	0644
runtime-config-logging.html	45446 bytes	0644
runtime-config-preset.html	8710 bytes	0644
runtime-config-query.html	24950 bytes	0644
runtime-config-replication.html	18294 bytes	0644
runtime-config-resource.html	27901 bytes	0644
runtime-config-short.html	6683 bytes	0644
runtime-config-statistics.html	8616 bytes	0644
runtime-config-wal.html	27093 bytes	0644
runtime-config.html	8249 bytes	0644
runtime.html	5241 bytes	0644
seg.html	15470 bytes	0644
sepgsql.html	30829 bytes	0644
server-programming.html	9618 bytes	0644
server-shutdown.html	6469 bytes	0644
server-start.html	14217 bytes	0644
source-format.html	5133 bytes	0644
source.html	4071 bytes	0644
sourcerepo.html	3411 bytes	0644
spgist-examples.html	2703 bytes	0644
spgist-extensibility.html	31282 bytes	0644
spgist-implementation.html	8098 bytes	0644
spgist-intro.html	4323 bytes	0644
spgist.html	2966 bytes	0644
spi-examples.html	6217 bytes	0644
spi-interface-support.html	3770 bytes	0644
spi-interface.html	5998 bytes	0644
spi-memory.html	7089 bytes	0644
spi-realloc.html	3627 bytes	0644
spi-spi-connect.html	4052 bytes	0644
spi-spi-copytuple.html	3453 bytes	0644
spi-spi-cursor-close.html	3336 bytes	0644
spi-spi-cursor-fetch.html	4110 bytes	0644
spi-spi-cursor-find.html	3464 bytes	0644
spi-spi-cursor-move.html	3890 bytes	0644
spi-spi-cursor-open-with-args.html	6178 bytes	0644
spi-spi-cursor-open-with-paramlist.html	5035 bytes	0644
spi-spi-cursor-open.html	5732 bytes	0644
spi-spi-exec.html	3591 bytes	0644
spi-spi-execp.html	4866 bytes	0644
spi-spi-execute-plan-with-paramlist.html	4893 bytes	0644
spi-spi-execute-plan.html	5901 bytes	0644
spi-spi-execute-with-args.html	6221 bytes	0644
spi-spi-execute.html	12598 bytes	0644
spi-spi-finish.html	3655 bytes	0644
spi-spi-fname.html	3767 bytes	0644
spi-spi-fnumber.html	3936 bytes	0644
spi-spi-freeplan.html	3505 bytes	0644
spi-spi-freetuple.html	3277 bytes	0644
spi-spi-freetupletable.html	3628 bytes	0644
spi-spi-getargcount.html	3698 bytes	0644
spi-spi-getargtypeid.html	4141 bytes	0644
spi-spi-getbinval.html	4287 bytes	0644
spi-spi-getnspname.html	3467 bytes	0644
spi-spi-getrelname.html	3351 bytes	0644
spi-spi-gettype.html	3714 bytes	0644
spi-spi-gettypeid.html	3718 bytes	0644
spi-spi-getvalue.html	4166 bytes	0644
spi-spi-is-cursor-plan.html	4560 bytes	0644
spi-spi-keepplan.html	3884 bytes	0644
spi-spi-modifytuple.html	5631 bytes	0644
spi-spi-palloc.html	3157 bytes	0644
spi-spi-pfree.html	3275 bytes	0644
spi-spi-pop.html	2743 bytes	0644
spi-spi-prepare-cursor.html	5055 bytes	0644
spi-spi-prepare-params.html	4412 bytes	0644
spi-spi-prepare.html	7661 bytes	0644
spi-spi-push.html	3737 bytes	0644
spi-spi-returntuple.html	4097 bytes	0644
spi-spi-saveplan.html	4576 bytes	0644
spi-spi-scroll-cursor-fetch.html	4809 bytes	0644
spi-spi-scroll-cursor-move.html	4899 bytes	0644
spi-visibility.html	4152 bytes	0644
spi.html	10843 bytes	0644
sql-abort.html	4177 bytes	0644
sql-alteraggregate.html	6111 bytes	0644
sql-altercollation.html	5084 bytes	0644
sql-alterconversion.html	5170 bytes	0644
sql-alterdatabase.html	8778 bytes	0644
sql-alterdefaultprivileges.html	9407 bytes	0644
sql-alterdomain.html	11113 bytes	0644
sql-alterextension.html	11745 bytes	0644
sql-alterforeigndatawrapper.html	7378 bytes	0644
sql-alterforeigntable.html	12707 bytes	0644
sql-alterfunction.html	12845 bytes	0644
sql-altergroup.html	5239 bytes	0644
sql-alterindex.html	7655 bytes	0644
sql-alterlanguage.html	4022 bytes	0644
sql-alterlargeobject.html	3730 bytes	0644
sql-alteropclass.html	5114 bytes	0644
sql-alteroperator.html	5435 bytes	0644
sql-alteropfamily.html	13564 bytes	0644
sql-alterrole.html	13028 bytes	0644
sql-alterschema.html	4314 bytes	0644
sql-altersequence.html	13031 bytes	0644
sql-alterserver.html	5928 bytes	0644
sql-altertable.html	43543 bytes	0644
sql-altertablespace.html	5866 bytes	0644
sql-altertrigger.html	4647 bytes	0644
sql-altertsconfig.html	8126 bytes	0644
sql-altertsdictionary.html	6539 bytes	0644
sql-altertsparser.html	4257 bytes	0644
sql-altertstemplate.html	4223 bytes	0644
sql-altertype.html	11193 bytes	0644
sql-alteruser.html	4720 bytes	0644
sql-alterusermapping.html	5714 bytes	0644
sql-alterview.html	6969 bytes	0644
sql-analyze.html	10674 bytes	0644
sql-begin.html	6695 bytes	0644
sql-checkpoint.html	3758 bytes	0644
sql-close.html	4984 bytes	0644
sql-cluster.html	9404 bytes	0644
sql-commands.html	18810 bytes	0644
sql-comment.html	13799 bytes	0644
sql-commit-prepared.html	4516 bytes	0644
sql-commit.html	3992 bytes	0644
sql-copy.html	37443 bytes	0644
sql-createaggregate.html	13829 bytes	0644
sql-createcast.html	19632 bytes	0644
sql-createcollation.html	6739 bytes	0644
sql-createconversion.html	6538 bytes	0644
sql-createdatabase.html	12133 bytes	0644
sql-createdomain.html	8544 bytes	0644
sql-createextension.html	9083 bytes	0644
sql-createforeigndatawrapper.html	8059 bytes	0644
sql-createforeigntable.html	7718 bytes	0644
sql-createfunction.html	31076 bytes	0644
sql-creategroup.html	4012 bytes	0644
sql-createindex.html	25934 bytes	0644
sql-createlanguage.html	14888 bytes	0644
sql-createopclass.html	12676 bytes	0644
sql-createoperator.html	10688 bytes	0644
sql-createopfamily.html	5626 bytes	0644
sql-createrole.html	19325 bytes	0644
sql-createrule.html	12656 bytes	0644
sql-createschema.html	8319 bytes	0644
sql-createsequence.html	13862 bytes	0644
sql-createserver.html	6251 bytes	0644
sql-createtable.html	59172 bytes	0644
sql-createtableas.html	12772 bytes	0644
sql-createtablespace.html	6104 bytes	0644
sql-createtrigger.html	23175 bytes	0644
sql-createtsconfig.html	5352 bytes	0644
sql-createtsdictionary.html	5533 bytes	0644
sql-createtsparser.html	5947 bytes	0644
sql-createtstemplate.html	5437 bytes	0644
sql-createtype.html	39460 bytes	0644
sql-createuser.html	4524 bytes	0644
sql-createusermapping.html	5503 bytes	0644
sql-createview.html	10556 bytes	0644
sql-deallocate.html	3785 bytes	0644
sql-declare.html	15400 bytes	0644
sql-delete.html	11777 bytes	0644
sql-discard.html	4309 bytes	0644
sql-do.html	5204 bytes	0644
sql-drop-owned.html	5058 bytes	0644
sql-dropaggregate.html	4561 bytes	0644
sql-dropcast.html	4344 bytes	0644
sql-dropcollation.html	4409 bytes	0644
sql-dropconversion.html	4437 bytes	0644
sql-dropdatabase.html	4344 bytes	0644
sql-dropdomain.html	4257 bytes	0644
sql-dropextension.html	4785 bytes	0644
sql-dropforeigndatawrapper.html	4526 bytes	0644
sql-dropforeigntable.html	4560 bytes	0644
sql-dropfunction.html	5838 bytes	0644
sql-dropgroup.html	3047 bytes	0644
sql-dropindex.html	5182 bytes	0644
sql-droplanguage.html	4841 bytes	0644
sql-dropopclass.html	5678 bytes	0644
sql-dropoperator.html	5222 bytes	0644
sql-dropopfamily.html	5279 bytes	0644
sql-droprole.html	5158 bytes	0644
sql-droprule.html	4151 bytes	0644
sql-dropschema.html	4529 bytes	0644
sql-dropsequence.html	4367 bytes	0644
sql-dropserver.html	4265 bytes	0644
sql-droptable.html	5028 bytes	0644
sql-droptablespace.html	4585 bytes	0644
sql-droptrigger.html	4711 bytes	0644
sql-droptsconfig.html	4772 bytes	0644
sql-droptsdictionary.html	4689 bytes	0644
sql-droptsparser.html	4595 bytes	0644
sql-droptstemplate.html	4567 bytes	0644
sql-droptype.html	4463 bytes	0644
sql-dropuser.html	3181 bytes	0644
sql-dropusermapping.html	4679 bytes	0644
sql-dropview.html	4262 bytes	0644
sql-end.html	4157 bytes	0644
sql-execute.html	5073 bytes	0644
sql-explain.html	17094 bytes	0644
sql-expressions.html	47801 bytes	0644
sql-fetch.html	14251 bytes	0644
sql-grant.html	29245 bytes	0644
sql-insert.html	12860 bytes	0644
sql-keywords-appendix.html	106534 bytes	0644
sql-listen.html	5903 bytes	0644
sql-load.html	4207 bytes	0644
sql-lock.html	11869 bytes	0644
sql-move.html	4984 bytes	0644
sql-notify.html	10948 bytes	0644
sql-prepare-transaction.html	8640 bytes	0644
sql-prepare.html	9181 bytes	0644
sql-reassign-owned.html	5344 bytes	0644
sql-reindex.html	11103 bytes	0644
sql-release-savepoint.html	5005 bytes	0644
sql-reset.html	4993 bytes	0644
sql-revoke.html	14879 bytes	0644
sql-rollback-prepared.html	4627 bytes	0644
sql-rollback-to.html	6401 bytes	0644
sql-rollback.html	3996 bytes	0644
sql-savepoint.html	5605 bytes	0644
sql-security-label.html	8879 bytes	0644
sql-select.html	79544 bytes	0644
sql-selectinto.html	7634 bytes	0644
sql-set-constraints.html	7068 bytes	0644
sql-set-role.html	6915 bytes	0644
sql-set-session-authorization.html	6062 bytes	0644
sql-set-transaction.html	12696 bytes	0644
sql-set.html	12057 bytes	0644
sql-show.html	6851 bytes	0644
sql-start-transaction.html	4983 bytes	0644
sql-syntax-calling-funcs.html	8080 bytes	0644
sql-syntax-lexical.html	43370 bytes	0644
sql-syntax.html	5430 bytes	0644
sql-truncate.html	9364 bytes	0644
sql-unlisten.html	4923 bytes	0644
sql-update.html	15669 bytes	0644
sql-vacuum.html	10669 bytes	0644
sql-values.html	10640 bytes	0644
sql.html	13569 bytes	0644
ssh-tunnels.html	6263 bytes	0644
ssl-tcp.html	13477 bytes	0644
sslinfo.html	7594 bytes	0644
standby-settings.html	5427 bytes	0644
storage-file-layout.html	12936 bytes	0644
storage-fsm.html	3821 bytes	0644
storage-init.html	2760 bytes	0644
storage-page-layout.html	13891 bytes	0644
storage-toast.html	11478 bytes	0644
storage-vm.html	3540 bytes	0644
storage.html	2952 bytes	0644
stylesheet.css	1538 bytes	0644
supported-platforms.html	5042 bytes	0644
tablefunc.html	32193 bytes	0644
tcn.html	4974 bytes	0644
test-parser.html	4530 bytes	0644
textsearch-configuration.html	6257 bytes	0644
textsearch-controls.html	26966 bytes	0644
textsearch-debugging.html	17227 bytes	0644
textsearch-dictionaries.html	31261 bytes	0644
textsearch-features.html	21310 bytes	0644
textsearch-indexes.html	7387 bytes	0644
textsearch-intro.html	18453 bytes	0644
textsearch-limitations.html	3859 bytes	0644
textsearch-migration.html	5034 bytes	0644
textsearch-parsers.html	9210 bytes	0644
textsearch-psql.html	9345 bytes	0644
textsearch-tables.html	9750 bytes	0644
textsearch.html	5878 bytes	0644
transaction-iso.html	27240 bytes	0644
trigger-datachanges.html	5072 bytes	0644
trigger-definition.html	15507 bytes	0644
trigger-example.html	7749 bytes	0644
trigger-interface.html	10719 bytes	0644
triggers.html	3798 bytes	0644
tsearch2.html	9950 bytes	0644
tutorial-accessdb.html	7040 bytes	0644
tutorial-advanced-intro.html	3341 bytes	0644
tutorial-advanced.html	2856 bytes	0644
tutorial-agg.html	7594 bytes	0644
tutorial-arch.html	4852 bytes	0644
tutorial-concepts.html	3839 bytes	0644
tutorial-conclusion.html	2849 bytes	0644
tutorial-createdb.html	9200 bytes	0644
tutorial-delete.html	3517 bytes	0644
tutorial-fk.html	4422 bytes	0644
tutorial-inheritance.html	6137 bytes	0644
tutorial-install.html	4522 bytes	0644
tutorial-join.html	9685 bytes	0644
tutorial-populate.html	4839 bytes	0644
tutorial-select.html	8033 bytes	0644
tutorial-sql-intro.html	4904 bytes	0644
tutorial-sql.html	3060 bytes	0644
tutorial-start.html	2629 bytes	0644
tutorial-table.html	5704 bytes	0644
tutorial-transactions.html	9948 bytes	0644
tutorial-update.html	3159 bytes	0644
tutorial-views.html	3375 bytes	0644
tutorial-window.html	12481 bytes	0644
tutorial.html	5209 bytes	0644
typeconv-func.html	12170 bytes	0644
typeconv-oper.html	14907 bytes	0644
typeconv-overview.html	8301 bytes	0644
typeconv-query.html	5450 bytes	0644
typeconv-union-case.html	6612 bytes	0644
typeconv.html	3721 bytes	0644
unaccent.html	6742 bytes	0644
unsupported-features-sql-standard.html	35115 bytes	0644
upgrading.html	12795 bytes	0644
user-manag.html	3983 bytes	0644
using-explain.html	41824 bytes	0644
uuid-ossp.html	7228 bytes	0644
vacuumlo.html	7548 bytes	0644
view-pg-available-extension-versions.html	4642 bytes	0644
view-pg-available-extensions.html	3944 bytes	0644
view-pg-cursors.html	5669 bytes	0644
view-pg-group.html	3897 bytes	0644
view-pg-indexes.html	4155 bytes	0644
view-pg-locks.html	14444 bytes	0644
view-pg-prepared-statements.html	5060 bytes	0644
view-pg-prepared-xacts.html	4912 bytes	0644
view-pg-roles.html	6073 bytes	0644
view-pg-rules.html	3999 bytes	0644
view-pg-seclabels.html	5123 bytes	0644
view-pg-settings.html	10600 bytes	0644
view-pg-shadow.html	5381 bytes	0644
view-pg-stats.html	8887 bytes	0644
view-pg-tables.html	4836 bytes	0644
view-pg-timezone-abbrevs.html	3860 bytes	0644
view-pg-timezone-names.html	4177 bytes	0644
view-pg-user-mappings.html	5165 bytes	0644
view-pg-user.html	4517 bytes	0644
view-pg-views.html	3853 bytes	0644
views-overview.html	6542 bytes	0644
wal-async-commit.html	9016 bytes	0644
wal-configuration.html	14960 bytes	0644
wal-internals.html	6151 bytes	0644
wal-intro.html	5534 bytes	0644
wal-reliability.html	11479 bytes	0644
wal.html	2928 bytes	0644
warm-standby-failover.html	6102 bytes	0644
warm-standby.html	34646 bytes	0644
xaggr.html	9902 bytes	0644
xfunc-c.html	78520 bytes	0644
xfunc-internal.html	4004 bytes	0644
xfunc-overload.html	5911 bytes	0644
xfunc-pl.html	2991 bytes	0644
xfunc-sql.html	38027 bytes	0644
xfunc-volatility.html	9839 bytes	0644
xfunc.html	4518 bytes	0644
xindex.html	44593 bytes	0644
xml2.html	16900 bytes	0644
xoper-optimization.html	23144 bytes	0644
xoper.html	4835 bytes	0644
xplang-install.html	11127 bytes	0644
xplang.html	4235 bytes	0644
xtypes.html	12114 bytes	0644