Na}{

Path: ~//proc/thread-self/root/opt/alt/postgresql11/usr/share/doc/alt-postgresql11-9.2.24/html/

File Content: runtime-config-logging.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Error Reporting and Logging</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="Server Configuration"
HREF="runtime-config.html"><LINK
REL="PREVIOUS"
TITLE="Query Planning"
HREF="runtime-config-query.html"><LINK
REL="NEXT"
TITLE="Run-time Statistics"
HREF="runtime-config-statistics.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="Query Planning"
HREF="runtime-config-query.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
HREF="runtime-config.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="60%"
ALIGN="center"
VALIGN="bottom"
>Chapter 18. Server Configuration</TD
><TD
WIDTH="20%"
ALIGN="right"
VALIGN="top"
><A
TITLE="Run-time Statistics"
HREF="runtime-config-statistics.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="RUNTIME-CONFIG-LOGGING"
>18.8. Error Reporting and Logging</A
></H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="RUNTIME-CONFIG-LOGGING-WHERE"
>18.8.1. Where To Log</A
></H2
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="GUC-LOG-DESTINATION"
></A
><TT
CLASS="VARNAME"
>log_destination</TT
> (<TT
CLASS="TYPE"
>string</TT
>)</DT
><DD
><P
>        <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> supports several methods
         for logging server messages, including
         <SPAN
CLASS="SYSTEMITEM"
>stderr</SPAN
>, <SPAN
CLASS="SYSTEMITEM"
>csvlog</SPAN
> and
         <SPAN
CLASS="SYSTEMITEM"
>syslog</SPAN
>. On Windows,
         <SPAN
CLASS="SYSTEMITEM"
>eventlog</SPAN
> is also supported. Set this
         parameter to a list of desired log destinations separated by
         commas. The default is to log to <SPAN
CLASS="SYSTEMITEM"
>stderr</SPAN
>
         only.
         This parameter can only be set in the <TT
CLASS="FILENAME"
>postgresql.conf</TT
>
         file or on the server command line.
       </P
><P
>        If <SPAN
CLASS="SYSTEMITEM"
>csvlog</SPAN
> is included in <TT
CLASS="VARNAME"
>log_destination</TT
>,
        log entries are output in <SPAN
CLASS="QUOTE"
>"comma separated
        value"</SPAN
> (<ACRONYM
CLASS="ACRONYM"
>CSV</ACRONYM
>) format, which is convenient for
        loading logs into programs.
        See <A
HREF="runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-CSVLOG"
>Section 18.8.4</A
> for details.
        <A
HREF="runtime-config-logging.html#GUC-LOGGING-COLLECTOR"
>logging_collector</A
> must be enabled to generate
        CSV-format log output.
       </P
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
>         On most Unix systems, you will need to alter the configuration of
         your system's <SPAN
CLASS="APPLICATION"
>syslog</SPAN
> daemon in order
         to make use of the <SPAN
CLASS="SYSTEMITEM"
>syslog</SPAN
> option for
         <TT
CLASS="VARNAME"
>log_destination</TT
>.  <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
>
         can log to <SPAN
CLASS="APPLICATION"
>syslog</SPAN
> facilities
         <TT
CLASS="LITERAL"
>LOCAL0</TT
> through <TT
CLASS="LITERAL"
>LOCAL7</TT
> (see <A
HREF="runtime-config-logging.html#GUC-SYSLOG-FACILITY"
>syslog_facility</A
>), but the default
         <SPAN
CLASS="APPLICATION"
>syslog</SPAN
> configuration on most platforms
         will discard all such messages.  You will need to add something like:
</P><PRE
CLASS="PROGRAMLISTING"
>local0.*    /var/log/postgresql</PRE
><P>
         to the  <SPAN
CLASS="APPLICATION"
>syslog</SPAN
> daemon's configuration file
         to make it work.
        </P
><P
>         On Windows, when you use the <TT
CLASS="LITERAL"
>eventlog</TT
>
         option for <TT
CLASS="VARNAME"
>log_destination</TT
>, you should
         register an event source and its library with the operating
         system so that the Windows Event Viewer can display event
         log messages cleanly.
         See <A
HREF="event-log-registration.html"
>Section 17.11</A
> for details.
        </P
></BLOCKQUOTE
></DIV
></DD
><DT
><A
NAME="GUC-LOGGING-COLLECTOR"
></A
><TT
CLASS="VARNAME"
>logging_collector</TT
> (<TT
CLASS="TYPE"
>boolean</TT
>)</DT
><DD
><P
>         This parameter enables the <I
CLASS="FIRSTTERM"
>logging collector</I
>, which
         is a background process that captures log messages
         sent to <SPAN
CLASS="SYSTEMITEM"
>stderr</SPAN
> and redirects them into log files.
         This approach is often more useful than
         logging to <SPAN
CLASS="APPLICATION"
>syslog</SPAN
>, since some types of messages
         might not appear in <SPAN
CLASS="APPLICATION"
>syslog</SPAN
> output.  (One common
         example is dynamic-linker failure messages; another is error messages
         produced by scripts such as <TT
CLASS="VARNAME"
>archive_command</TT
>.)
         This parameter can only be set at server start.
       </P
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
>         It is possible to log to <SPAN
CLASS="SYSTEMITEM"
>stderr</SPAN
> without using the
         logging collector; the log messages will just go to wherever the
         server's <SPAN
CLASS="SYSTEMITEM"
>stderr</SPAN
> is directed.  However, that method is
         only suitable for low log volumes, since it provides no convenient
         way to rotate log files.  Also, on some platforms not using the
         logging collector can result in lost or garbled log output, because
         multiple processes writing concurrently to the same log file can
         overwrite each other's output.
        </P
></BLOCKQUOTE
></DIV
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
>          The logging collector is designed to never lose messages.  This means
          that in case of extremely high load, server processes could be
          blocked while trying to send additional log messages when the
          collector has fallen behind.  In contrast, <SPAN
CLASS="APPLICATION"
>syslog</SPAN
>
          prefers to drop messages if it cannot write them, which means it
          may fail to log some messages in such cases but it will not block
          the rest of the system.
        </P
></BLOCKQUOTE
></DIV
></DD
><DT
><A
NAME="GUC-LOG-DIRECTORY"
></A
><TT
CLASS="VARNAME"
>log_directory</TT
> (<TT
CLASS="TYPE"
>string</TT
>)</DT
><DD
><P
>        When <TT
CLASS="VARNAME"
>logging_collector</TT
> is enabled,
        this parameter determines the directory in which log files will be created.
        It can be specified as an absolute path, or relative to the
        cluster data directory.
        This parameter can only be set in the <TT
CLASS="FILENAME"
>postgresql.conf</TT
>
        file or on the server command line.
        The default is <TT
CLASS="LITERAL"
>pg_log</TT
>.
       </P
></DD
><DT
><A
NAME="GUC-LOG-FILENAME"
></A
><TT
CLASS="VARNAME"
>log_filename</TT
> (<TT
CLASS="TYPE"
>string</TT
>)</DT
><DD
><P
>        When <TT
CLASS="VARNAME"
>logging_collector</TT
> is enabled,
        this parameter sets the file names of the created log files.  The value
        is treated as a <SPAN
CLASS="SYSTEMITEM"
>strftime</SPAN
> pattern,
        so <TT
CLASS="LITERAL"
>%</TT
>-escapes can be used to specify time-varying
        file names.  (Note that if there are
        any time-zone-dependent <TT
CLASS="LITERAL"
>%</TT
>-escapes, the computation
        is done in the zone specified
        by <A
HREF="runtime-config-logging.html#GUC-LOG-TIMEZONE"
>log_timezone</A
>.)
        The supported <TT
CLASS="LITERAL"
>%</TT
>-escapes are similar to those
        listed in the Open Group's <A
HREF="http://pubs.opengroup.org/onlinepubs/009695399/functions/strftime.html"
TARGET="_top"
>strftime
        </A
> specification.
        Note that the system's <SPAN
CLASS="SYSTEMITEM"
>strftime</SPAN
> is not used
        directly, so platform-specific (nonstandard) extensions do not work.
        The default is <TT
CLASS="LITERAL"
>postgresql-%Y-%m-%d_%H%M%S.log</TT
>.
       </P
><P
>        If you specify a file name without escapes, you should plan to
        use a log rotation utility to avoid eventually filling the
        entire disk.  In releases prior to 8.4, if
        no <TT
CLASS="LITERAL"
>%</TT
> escapes were
        present, <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> would append
        the epoch of the new log file's creation time, but this is no
        longer the case.
       </P
><P
>        If CSV-format output is enabled in <TT
CLASS="VARNAME"
>log_destination</TT
>,
        <TT
CLASS="LITERAL"
>.csv</TT
> will be appended to the timestamped
        log file name to create the file name for CSV-format output.
        (If <TT
CLASS="VARNAME"
>log_filename</TT
> ends in <TT
CLASS="LITERAL"
>.log</TT
>, the suffix is
        replaced instead.)
       </P
><P
>        This parameter can only be set in the <TT
CLASS="FILENAME"
>postgresql.conf</TT
>
        file or on the server command line.
       </P
></DD
><DT
><A
NAME="GUC-LOG-FILE-MODE"
></A
><TT
CLASS="VARNAME"
>log_file_mode</TT
> (<TT
CLASS="TYPE"
>integer</TT
>)</DT
><DD
><P
>        On Unix systems this parameter sets the permissions for log files
        when <TT
CLASS="VARNAME"
>logging_collector</TT
> is enabled. (On Microsoft
        Windows this parameter is ignored.)
        The parameter value is expected to be a numeric mode
        specified in the format accepted by the
        <CODE
CLASS="FUNCTION"
>chmod</CODE
> and <CODE
CLASS="FUNCTION"
>umask</CODE
>
        system calls.  (To use the customary octal format the number
        must start with a <TT
CLASS="LITERAL"
>0</TT
> (zero).)
       </P
><P
>        The default permissions are <TT
CLASS="LITERAL"
>0600</TT
>, meaning only the
        server owner can read or write the log files.  The other commonly
        useful setting is <TT
CLASS="LITERAL"
>0640</TT
>, allowing members of the owner's
        group to read the files.  Note however that to make use of such a
        setting, you'll need to alter <A
HREF="runtime-config-logging.html#GUC-LOG-DIRECTORY"
>log_directory</A
> to
        store the files somewhere outside the cluster data directory.  In
        any case, it's unwise to make the log files world-readable, since
        they might contain sensitive data.
       </P
><P
>        This parameter can only be set in the <TT
CLASS="FILENAME"
>postgresql.conf</TT
>
        file or on the server command line.
       </P
></DD
><DT
><A
NAME="GUC-LOG-ROTATION-AGE"
></A
><TT
CLASS="VARNAME"
>log_rotation_age</TT
> (<TT
CLASS="TYPE"
>integer</TT
>)</DT
><DD
><P
>        When <TT
CLASS="VARNAME"
>logging_collector</TT
> is enabled,
        this parameter determines the maximum lifetime of an individual log file.
        After this many minutes have elapsed, a new log file will
        be created.  Set to zero to disable time-based creation of
        new log files.
        This parameter can only be set in the <TT
CLASS="FILENAME"
>postgresql.conf</TT
>
        file or on the server command line.
       </P
></DD
><DT
><A
NAME="GUC-LOG-ROTATION-SIZE"
></A
><TT
CLASS="VARNAME"
>log_rotation_size</TT
> (<TT
CLASS="TYPE"
>integer</TT
>)</DT
><DD
><P
>        When <TT
CLASS="VARNAME"
>logging_collector</TT
> is enabled,
        this parameter determines the maximum size of an individual log file.
        After this many kilobytes have been emitted into a log file,
        a new log file will be created.  Set to zero to disable size-based
        creation of new log files.
        This parameter can only be set in the <TT
CLASS="FILENAME"
>postgresql.conf</TT
>
        file or on the server command line.
       </P
></DD
><DT
><A
NAME="GUC-LOG-TRUNCATE-ON-ROTATION"
></A
><TT
CLASS="VARNAME"
>log_truncate_on_rotation</TT
> (<TT
CLASS="TYPE"
>boolean</TT
>)</DT
><DD
><P
>        When <TT
CLASS="VARNAME"
>logging_collector</TT
> is enabled,
        this parameter will cause <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> to truncate (overwrite),
        rather than append to, any existing log file of the same name.
        However, truncation will occur only when a new file is being opened
        due to time-based rotation, not during server startup or size-based
        rotation.  When off, pre-existing files will be appended to in
        all cases.  For example, using this setting in combination with
        a <TT
CLASS="VARNAME"
>log_filename</TT
> like <TT
CLASS="LITERAL"
>postgresql-%H.log</TT
>
        would result in generating twenty-four hourly log files and then
        cyclically overwriting them.
        This parameter can only be set in the <TT
CLASS="FILENAME"
>postgresql.conf</TT
>
        file or on the server command line.
       </P
><P
>        Example:  To keep 7 days of logs, one log file per day named
        <TT
CLASS="LITERAL"
>server_log.Mon</TT
>, <TT
CLASS="LITERAL"
>server_log.Tue</TT
>,
        etc, and automatically overwrite last week's log with this week's log,
        set <TT
CLASS="VARNAME"
>log_filename</TT
> to <TT
CLASS="LITERAL"
>server_log.%a</TT
>,
        <TT
CLASS="VARNAME"
>log_truncate_on_rotation</TT
> to <TT
CLASS="LITERAL"
>on</TT
>, and
        <TT
CLASS="VARNAME"
>log_rotation_age</TT
> to <TT
CLASS="LITERAL"
>1440</TT
>.
       </P
><P
>        Example: To keep 24 hours of logs, one log file per hour, but
        also rotate sooner if the log file size exceeds 1GB, set
        <TT
CLASS="VARNAME"
>log_filename</TT
> to <TT
CLASS="LITERAL"
>server_log.%H%M</TT
>,
        <TT
CLASS="VARNAME"
>log_truncate_on_rotation</TT
> to <TT
CLASS="LITERAL"
>on</TT
>,
        <TT
CLASS="VARNAME"
>log_rotation_age</TT
> to <TT
CLASS="LITERAL"
>60</TT
>, and
        <TT
CLASS="VARNAME"
>log_rotation_size</TT
> to <TT
CLASS="LITERAL"
>1000000</TT
>.
        Including <TT
CLASS="LITERAL"
>%M</TT
> in <TT
CLASS="VARNAME"
>log_filename</TT
> allows
        any size-driven rotations that might occur to select a file name
        different from the hour's initial file name.
       </P
></DD
><DT
><A
NAME="GUC-SYSLOG-FACILITY"
></A
><TT
CLASS="VARNAME"
>syslog_facility</TT
> (<TT
CLASS="TYPE"
>enum</TT
>)</DT
><DD
><P
>        When logging to <SPAN
CLASS="APPLICATION"
>syslog</SPAN
> is enabled, this parameter
        determines the <SPAN
CLASS="APPLICATION"
>syslog</SPAN
>
        <SPAN
CLASS="QUOTE"
>"facility"</SPAN
> to be used.  You can choose
        from <TT
CLASS="LITERAL"
>LOCAL0</TT
>, <TT
CLASS="LITERAL"
>LOCAL1</TT
>,
        <TT
CLASS="LITERAL"
>LOCAL2</TT
>, <TT
CLASS="LITERAL"
>LOCAL3</TT
>, <TT
CLASS="LITERAL"
>LOCAL4</TT
>,
        <TT
CLASS="LITERAL"
>LOCAL5</TT
>, <TT
CLASS="LITERAL"
>LOCAL6</TT
>, <TT
CLASS="LITERAL"
>LOCAL7</TT
>;
        the default is <TT
CLASS="LITERAL"
>LOCAL0</TT
>. See also the
        documentation of your system's
        <SPAN
CLASS="APPLICATION"
>syslog</SPAN
> daemon.
        This parameter can only be set in the <TT
CLASS="FILENAME"
>postgresql.conf</TT
>
        file or on the server command line.
       </P
></DD
><DT
><A
NAME="GUC-SYSLOG-IDENT"
></A
><TT
CLASS="VARNAME"
>syslog_ident</TT
> (<TT
CLASS="TYPE"
>string</TT
>)</DT
><DD
><P
>         When logging to <SPAN
CLASS="APPLICATION"
>syslog</SPAN
> is enabled, this parameter
         determines the program name used to identify
         <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> messages in
         <SPAN
CLASS="APPLICATION"
>syslog</SPAN
> logs. The default is
         <TT
CLASS="LITERAL"
>postgres</TT
>.
         This parameter can only be set in the <TT
CLASS="FILENAME"
>postgresql.conf</TT
>
         file or on the server command line.
        </P
></DD
><DT
><A
NAME="GUC-EVENT-SOURCE"
></A
><TT
CLASS="VARNAME"
>event_source</TT
> (<TT
CLASS="TYPE"
>string</TT
>)</DT
><DD
><P
>        When logging to <SPAN
CLASS="APPLICATION"
>event log</SPAN
> is enabled, this parameter
        determines the program name used to identify
        <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> messages in
        the log. The default is <TT
CLASS="LITERAL"
>PostgreSQL</TT
>.
        This parameter can only be set in the <TT
CLASS="FILENAME"
>postgresql.conf</TT
>
        file or on the server command line.
       </P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="RUNTIME-CONFIG-LOGGING-WHEN"
>18.8.2. When To Log</A
></H2
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="GUC-CLIENT-MIN-MESSAGES"
></A
><TT
CLASS="VARNAME"
>client_min_messages</TT
> (<TT
CLASS="TYPE"
>enum</TT
>)</DT
><DD
><P
>        Controls which message levels are sent to the client.
        Valid values are <TT
CLASS="LITERAL"
>DEBUG5</TT
>,
        <TT
CLASS="LITERAL"
>DEBUG4</TT
>, <TT
CLASS="LITERAL"
>DEBUG3</TT
>, <TT
CLASS="LITERAL"
>DEBUG2</TT
>,
        <TT
CLASS="LITERAL"
>DEBUG1</TT
>, <TT
CLASS="LITERAL"
>LOG</TT
>, <TT
CLASS="LITERAL"
>NOTICE</TT
>,
        <TT
CLASS="LITERAL"
>WARNING</TT
>, <TT
CLASS="LITERAL"
>ERROR</TT
>, <TT
CLASS="LITERAL"
>FATAL</TT
>,
        and <TT
CLASS="LITERAL"
>PANIC</TT
>.  Each level
        includes all the levels that follow it.  The later the level,
        the fewer messages are sent.  The default is
        <TT
CLASS="LITERAL"
>NOTICE</TT
>.  Note that <TT
CLASS="LITERAL"
>LOG</TT
> has a different
        rank here than in <TT
CLASS="VARNAME"
>log_min_messages</TT
>.
       </P
></DD
><DT
><A
NAME="GUC-LOG-MIN-MESSAGES"
></A
><TT
CLASS="VARNAME"
>log_min_messages</TT
> (<TT
CLASS="TYPE"
>enum</TT
>)</DT
><DD
><P
>        Controls which message levels are written to the server log.
        Valid values are <TT
CLASS="LITERAL"
>DEBUG5</TT
>, <TT
CLASS="LITERAL"
>DEBUG4</TT
>,
        <TT
CLASS="LITERAL"
>DEBUG3</TT
>, <TT
CLASS="LITERAL"
>DEBUG2</TT
>, <TT
CLASS="LITERAL"
>DEBUG1</TT
>,
        <TT
CLASS="LITERAL"
>INFO</TT
>, <TT
CLASS="LITERAL"
>NOTICE</TT
>, <TT
CLASS="LITERAL"
>WARNING</TT
>,
        <TT
CLASS="LITERAL"
>ERROR</TT
>, <TT
CLASS="LITERAL"
>LOG</TT
>, <TT
CLASS="LITERAL"
>FATAL</TT
>, and
        <TT
CLASS="LITERAL"
>PANIC</TT
>.  Each level includes all the levels that
        follow it.  The later the level, the fewer messages are sent
        to the log.  The default is <TT
CLASS="LITERAL"
>WARNING</TT
>.  Note that
        <TT
CLASS="LITERAL"
>LOG</TT
> has a different rank here than in
        <TT
CLASS="VARNAME"
>client_min_messages</TT
>.
        Only superusers can change this setting.
       </P
></DD
><DT
><A
NAME="GUC-LOG-MIN-ERROR-STATEMENT"
></A
><TT
CLASS="VARNAME"
>log_min_error_statement</TT
> (<TT
CLASS="TYPE"
>enum</TT
>)</DT
><DD
><P
>        Controls which SQL statements that cause an error
        condition are recorded in the server log.  The current
        SQL statement is included in the log entry for any message of
        the specified severity or higher.
        Valid values are <TT
CLASS="LITERAL"
>DEBUG5</TT
>,
        <TT
CLASS="LITERAL"
>DEBUG4</TT
>, <TT
CLASS="LITERAL"
>DEBUG3</TT
>,
        <TT
CLASS="LITERAL"
>DEBUG2</TT
>, <TT
CLASS="LITERAL"
>DEBUG1</TT
>,
        <TT
CLASS="LITERAL"
>INFO</TT
>, <TT
CLASS="LITERAL"
>NOTICE</TT
>,
        <TT
CLASS="LITERAL"
>WARNING</TT
>, <TT
CLASS="LITERAL"
>ERROR</TT
>,
        <TT
CLASS="LITERAL"
>LOG</TT
>,
        <TT
CLASS="LITERAL"
>FATAL</TT
>, and <TT
CLASS="LITERAL"
>PANIC</TT
>.
        The default is <TT
CLASS="LITERAL"
>ERROR</TT
>, which means statements
        causing errors, log messages, fatal errors, or panics will be logged.
        To effectively turn off logging of failing statements,
        set this parameter to <TT
CLASS="LITERAL"
>PANIC</TT
>.
        Only superusers can change this setting.
       </P
></DD
><DT
><A
NAME="GUC-LOG-MIN-DURATION-STATEMENT"
></A
><TT
CLASS="VARNAME"
>log_min_duration_statement</TT
> (<TT
CLASS="TYPE"
>integer</TT
>)</DT
><DD
><P
>         Causes the duration of each completed statement to be logged
         if the statement ran for at least the specified number of
         milliseconds.  Setting this to zero prints all statement durations.
         Minus-one (the default) disables logging statement durations.
         For example, if you set it to <TT
CLASS="LITERAL"
>250ms</TT
>
         then all SQL statements that run 250ms or longer will be
         logged.  Enabling this parameter can be helpful in tracking down
         unoptimized queries in your applications.
         Only superusers can change this setting.
        </P
><P
>         For clients using extended query protocol, durations of the Parse,
         Bind, and Execute steps are logged independently.
        </P
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
>         When using this option together with
         <A
HREF="runtime-config-logging.html#GUC-LOG-STATEMENT"
>log_statement</A
>,
         the text of statements that are logged because of
         <TT
CLASS="VARNAME"
>log_statement</TT
> will not be repeated in the
         duration log message.
         If you are not using <SPAN
CLASS="APPLICATION"
>syslog</SPAN
>, it is recommended
         that you log the PID or session ID using
         <A
HREF="runtime-config-logging.html#GUC-LOG-LINE-PREFIX"
>log_line_prefix</A
>
         so that you can link the statement message to the later
         duration message using the process ID or session ID.
        </P
></BLOCKQUOTE
></DIV
></DD
></DL
></DIV
><P
>     <A
HREF="runtime-config-logging.html#RUNTIME-CONFIG-SEVERITY-LEVELS"
>Table 18-1</A
> explains the message
     severity levels used by <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
>.  If logging output
     is sent to <SPAN
CLASS="SYSTEMITEM"
>syslog</SPAN
> or Windows'
     <SPAN
CLASS="SYSTEMITEM"
>eventlog</SPAN
>, the severity levels are translated
     as shown in the table.
    </P
><DIV
CLASS="TABLE"
><A
NAME="RUNTIME-CONFIG-SEVERITY-LEVELS"
></A
><P
><B
>Table 18-1. Message Severity Levels</B
></P
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><COL><COL><COL><THEAD
><TR
><TH
>Severity</TH
><TH
>Usage</TH
><TH
><SPAN
CLASS="SYSTEMITEM"
>syslog</SPAN
></TH
><TH
><SPAN
CLASS="SYSTEMITEM"
>eventlog</SPAN
></TH
></TR
></THEAD
><TBODY
><TR
><TD
><TT
CLASS="LITERAL"
>DEBUG1..DEBUG5</TT
></TD
><TD
>Provides successively-more-detailed information for use by
         developers.</TD
><TD
><TT
CLASS="LITERAL"
>DEBUG</TT
></TD
><TD
><TT
CLASS="LITERAL"
>INFORMATION</TT
></TD
></TR
><TR
><TD
><TT
CLASS="LITERAL"
>INFO</TT
></TD
><TD
>Provides information implicitly requested by the user,
         e.g., output from <TT
CLASS="COMMAND"
>VACUUM VERBOSE</TT
>.</TD
><TD
><TT
CLASS="LITERAL"
>INFO</TT
></TD
><TD
><TT
CLASS="LITERAL"
>INFORMATION</TT
></TD
></TR
><TR
><TD
><TT
CLASS="LITERAL"
>NOTICE</TT
></TD
><TD
>Provides information that might be helpful to users, e.g.,
         notice of truncation of long identifiers.</TD
><TD
><TT
CLASS="LITERAL"
>NOTICE</TT
></TD
><TD
><TT
CLASS="LITERAL"
>INFORMATION</TT
></TD
></TR
><TR
><TD
><TT
CLASS="LITERAL"
>WARNING</TT
></TD
><TD
>Provides warnings of likely problems, e.g., <TT
CLASS="COMMAND"
>COMMIT</TT
>
         outside a transaction block.</TD
><TD
><TT
CLASS="LITERAL"
>NOTICE</TT
></TD
><TD
><TT
CLASS="LITERAL"
>WARNING</TT
></TD
></TR
><TR
><TD
><TT
CLASS="LITERAL"
>ERROR</TT
></TD
><TD
>Reports an error that caused the current command to
         abort.</TD
><TD
><TT
CLASS="LITERAL"
>WARNING</TT
></TD
><TD
><TT
CLASS="LITERAL"
>ERROR</TT
></TD
></TR
><TR
><TD
><TT
CLASS="LITERAL"
>LOG</TT
></TD
><TD
>Reports information of interest to administrators, e.g.,
         checkpoint activity.</TD
><TD
><TT
CLASS="LITERAL"
>INFO</TT
></TD
><TD
><TT
CLASS="LITERAL"
>INFORMATION</TT
></TD
></TR
><TR
><TD
><TT
CLASS="LITERAL"
>FATAL</TT
></TD
><TD
>Reports an error that caused the current session to
         abort.</TD
><TD
><TT
CLASS="LITERAL"
>ERR</TT
></TD
><TD
><TT
CLASS="LITERAL"
>ERROR</TT
></TD
></TR
><TR
><TD
><TT
CLASS="LITERAL"
>PANIC</TT
></TD
><TD
>Reports an error that caused all database sessions to abort.</TD
><TD
><TT
CLASS="LITERAL"
>CRIT</TT
></TD
><TD
><TT
CLASS="LITERAL"
>ERROR</TT
></TD
></TR
></TBODY
></TABLE
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="RUNTIME-CONFIG-LOGGING-WHAT"
>18.8.3. What To Log</A
></H2
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
><A
NAME="GUC-APPLICATION-NAME"
></A
><TT
CLASS="VARNAME"
>application_name</TT
> (<TT
CLASS="TYPE"
>string</TT
>)</DT
><DD
><P
>        The <TT
CLASS="VARNAME"
>application_name</TT
> can be any string of less than
        <TT
CLASS="SYMBOL"
>NAMEDATALEN</TT
> characters (64 characters in a standard build).
        It is typically set by an application upon connection to the server.
        The name will be displayed in the <TT
CLASS="STRUCTNAME"
>pg_stat_activity</TT
> view
        and included in CSV log entries.  It can also be included in regular
        log entries via the <A
HREF="runtime-config-logging.html#GUC-LOG-LINE-PREFIX"
>log_line_prefix</A
> parameter.
        Only printable ASCII characters may be used in the
        <TT
CLASS="VARNAME"
>application_name</TT
> value. Other characters will be
        replaced with question marks (<TT
CLASS="LITERAL"
>?</TT
>).
       </P
></DD
><DT
><TT
CLASS="VARNAME"
>debug_print_parse</TT
> (<TT
CLASS="TYPE"
>boolean</TT
>)<BR><TT
CLASS="VARNAME"
>debug_print_rewritten</TT
> (<TT
CLASS="TYPE"
>boolean</TT
>)<BR><TT
CLASS="VARNAME"
>debug_print_plan</TT
> (<TT
CLASS="TYPE"
>boolean</TT
>)</DT
><DD
><P
>        These parameters enable various debugging output to be emitted.
        When set, they print the resulting parse tree, the query rewriter
        output, or the execution plan for each executed query.
        These messages are emitted at <TT
CLASS="LITERAL"
>LOG</TT
> message level, so by
        default they will appear in the server log but will not be sent to the
        client.  You can change that by adjusting
        <A
HREF="runtime-config-logging.html#GUC-CLIENT-MIN-MESSAGES"
>client_min_messages</A
> and/or
        <A
HREF="runtime-config-logging.html#GUC-LOG-MIN-MESSAGES"
>log_min_messages</A
>.
        These parameters are off by default.
       </P
></DD
><DT
><TT
CLASS="VARNAME"
>debug_pretty_print</TT
> (<TT
CLASS="TYPE"
>boolean</TT
>)</DT
><DD
><P
>        When set, <TT
CLASS="VARNAME"
>debug_pretty_print</TT
> indents the messages
        produced by <TT
CLASS="VARNAME"
>debug_print_parse</TT
>,
        <TT
CLASS="VARNAME"
>debug_print_rewritten</TT
>, or
        <TT
CLASS="VARNAME"
>debug_print_plan</TT
>.  This results in more readable
        but much longer output than the <SPAN
CLASS="QUOTE"
>"compact"</SPAN
> format used when
        it is off.  It is on by default.
       </P
></DD
><DT
><A
NAME="GUC-LOG-CHECKPOINTS"
></A
><TT
CLASS="VARNAME"
>log_checkpoints</TT
> (<TT
CLASS="TYPE"
>boolean</TT
>)</DT
><DD
><P
>        Causes checkpoints and restartpoints to be logged in the server log.
        Some statistics are included in the log messages, including the number
        of buffers written and the time spent writing them.
        This parameter can only be set in the <TT
CLASS="FILENAME"
>postgresql.conf</TT
>
        file or on the server command line. The default is off.
       </P
></DD
><DT
><A
NAME="GUC-LOG-CONNECTIONS"
></A
><TT
CLASS="VARNAME"
>log_connections</TT
> (<TT
CLASS="TYPE"
>boolean</TT
>)</DT
><DD
><P
>        Causes each attempted connection to the server to be logged,
        as well as successful completion of client authentication.
        This parameter cannot be changed after session start.
        The default is off.
       </P
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
>         Some client programs, like <SPAN
CLASS="APPLICATION"
>psql</SPAN
>, attempt
         to connect twice while determining if a password is required, so
         duplicate <SPAN
CLASS="QUOTE"
>"connection received"</SPAN
> messages do not
         necessarily indicate a problem.
        </P
></BLOCKQUOTE
></DIV
></DD
><DT
><A
NAME="GUC-LOG-DISCONNECTIONS"
></A
><TT
CLASS="VARNAME"
>log_disconnections</TT
> (<TT
CLASS="TYPE"
>boolean</TT
>)</DT
><DD
><P
>        This outputs a line in the server log similar to
        <TT
CLASS="VARNAME"
>log_connections</TT
> but at session termination,
        and includes the duration of the session.  This is off by
        default.
        This parameter cannot be changed after session start.
       </P
></DD
><DT
><A
NAME="GUC-LOG-DURATION"
></A
><TT
CLASS="VARNAME"
>log_duration</TT
> (<TT
CLASS="TYPE"
>boolean</TT
>)</DT
><DD
><P
>        Causes the duration of every completed statement to be logged.
        The default is <TT
CLASS="LITERAL"
>off</TT
>.
        Only superusers can change this setting.
       </P
><P
>        For clients using extended query protocol, durations of the Parse,
        Bind, and Execute steps are logged independently.
       </P
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
>         The difference between setting this option and setting
         <A
HREF="runtime-config-logging.html#GUC-LOG-MIN-DURATION-STATEMENT"
>log_min_duration_statement</A
> to zero is that
         exceeding <TT
CLASS="VARNAME"
>log_min_duration_statement</TT
> forces the text of
         the query to be logged, but this option doesn't.  Thus, if
         <TT
CLASS="VARNAME"
>log_duration</TT
> is <TT
CLASS="LITERAL"
>on</TT
> and
         <TT
CLASS="VARNAME"
>log_min_duration_statement</TT
> has a positive value, all
         durations are logged but the query text is included only for
         statements exceeding the threshold.  This behavior can be useful for
         gathering statistics in high-load installations.
        </P
></BLOCKQUOTE
></DIV
></DD
><DT
><A
NAME="GUC-LOG-ERROR-VERBOSITY"
></A
><TT
CLASS="VARNAME"
>log_error_verbosity</TT
> (<TT
CLASS="TYPE"
>enum</TT
>)</DT
><DD
><P
>        Controls the amount of detail written in the server log for each
        message that is logged.  Valid values are <TT
CLASS="LITERAL"
>TERSE</TT
>,
        <TT
CLASS="LITERAL"
>DEFAULT</TT
>, and <TT
CLASS="LITERAL"
>VERBOSE</TT
>, each adding more
        fields to displayed messages.  <TT
CLASS="LITERAL"
>TERSE</TT
> excludes
        the logging of <TT
CLASS="LITERAL"
>DETAIL</TT
>, <TT
CLASS="LITERAL"
>HINT</TT
>,
        <TT
CLASS="LITERAL"
>QUERY</TT
>, and <TT
CLASS="LITERAL"
>CONTEXT</TT
> error information.
        <TT
CLASS="LITERAL"
>VERBOSE</TT
> output includes the <TT
CLASS="SYMBOL"
>SQLSTATE</TT
> error
        code (see also <A
HREF="errcodes-appendix.html"
>Appendix A</A
>) and the source code file name, function name,
        and line number that generated the error.
        Only superusers can change this setting.
       </P
></DD
><DT
><A
NAME="GUC-LOG-HOSTNAME"
></A
><TT
CLASS="VARNAME"
>log_hostname</TT
> (<TT
CLASS="TYPE"
>boolean</TT
>)</DT
><DD
><P
>        By default, connection log messages only show the IP address of the
        connecting host. Turning this parameter on causes logging of the
        host name as well.  Note that depending on your host name resolution
        setup this might impose a non-negligible performance penalty.
        This parameter can only be set in the <TT
CLASS="FILENAME"
>postgresql.conf</TT
>
        file or on the server command line.
       </P
></DD
><DT
><A
NAME="GUC-LOG-LINE-PREFIX"
></A
><TT
CLASS="VARNAME"
>log_line_prefix</TT
> (<TT
CLASS="TYPE"
>string</TT
>)</DT
><DD
><P
>         This is a <CODE
CLASS="FUNCTION"
>printf</CODE
>-style string that is output at the
         beginning of each log line.
         <TT
CLASS="LITERAL"
>%</TT
> characters begin <SPAN
CLASS="QUOTE"
>"escape sequences"</SPAN
>
         that are replaced with status information as outlined below.
         Unrecognized escapes are ignored. Other
         characters are copied straight to the log line. Some escapes are
         only recognized by session processes, and are ignored by
         background processes such as the main server process.
         This parameter can only be set in the <TT
CLASS="FILENAME"
>postgresql.conf</TT
>
         file or on the server command line. The default is an empty string.

<DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN29710"
></A
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><COL><COL><THEAD
><TR
><TH
>Escape</TH
><TH
>Effect</TH
><TH
>Session only</TH
></TR
></THEAD
><TBODY
><TR
><TD
><TT
CLASS="LITERAL"
>%a</TT
></TD
><TD
>Application name</TD
><TD
>yes</TD
></TR
><TR
><TD
><TT
CLASS="LITERAL"
>%u</TT
></TD
><TD
>User name</TD
><TD
>yes</TD
></TR
><TR
><TD
><TT
CLASS="LITERAL"
>%d</TT
></TD
><TD
>Database name</TD
><TD
>yes</TD
></TR
><TR
><TD
><TT
CLASS="LITERAL"
>%r</TT
></TD
><TD
>Remote host name or IP address, and remote port</TD
><TD
>yes</TD
></TR
><TR
><TD
><TT
CLASS="LITERAL"
>%h</TT
></TD
><TD
>Remote host name or IP address</TD
><TD
>yes</TD
></TR
><TR
><TD
><TT
CLASS="LITERAL"
>%p</TT
></TD
><TD
>Process ID</TD
><TD
>no</TD
></TR
><TR
><TD
><TT
CLASS="LITERAL"
>%t</TT
></TD
><TD
>Time stamp without milliseconds</TD
><TD
>no</TD
></TR
><TR
><TD
><TT
CLASS="LITERAL"
>%m</TT
></TD
><TD
>Time stamp with milliseconds</TD
><TD
>no</TD
></TR
><TR
><TD
><TT
CLASS="LITERAL"
>%i</TT
></TD
><TD
>Command tag: type of session's current command</TD
><TD
>yes</TD
></TR
><TR
><TD
><TT
CLASS="LITERAL"
>%e</TT
></TD
><TD
>SQLSTATE error code</TD
><TD
>no</TD
></TR
><TR
><TD
><TT
CLASS="LITERAL"
>%c</TT
></TD
><TD
>Session ID: see below</TD
><TD
>no</TD
></TR
><TR
><TD
><TT
CLASS="LITERAL"
>%l</TT
></TD
><TD
>Number of the log line for each session or process, starting at 1</TD
><TD
>no</TD
></TR
><TR
><TD
><TT
CLASS="LITERAL"
>%s</TT
></TD
><TD
>Process start time stamp</TD
><TD
>no</TD
></TR
><TR
><TD
><TT
CLASS="LITERAL"
>%v</TT
></TD
><TD
>Virtual transaction ID (backendID/localXID)</TD
><TD
>no</TD
></TR
><TR
><TD
><TT
CLASS="LITERAL"
>%x</TT
></TD
><TD
>Transaction ID (0 if none is assigned)</TD
><TD
>no</TD
></TR
><TR
><TD
><TT
CLASS="LITERAL"
>%q</TT
></TD
><TD
>Produces no output, but tells non-session
             processes to stop at this point in the string; ignored by
             session processes</TD
><TD
>no</TD
></TR
><TR
><TD
><TT
CLASS="LITERAL"
>%%</TT
></TD
><TD
>Literal <TT
CLASS="LITERAL"
>%</TT
></TD
><TD
>no</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
>

The <TT
CLASS="LITERAL"
>%c</TT
> escape prints a quasi-unique session identifier,
         consisting of two 4-byte hexadecimal numbers (without leading zeros)
         separated by a dot.  The numbers are the process start time and the
         process ID, so <TT
CLASS="LITERAL"
>%c</TT
> can also be used as a space saving way
         of printing those items.  For example, to generate the session
         identifier from <TT
CLASS="LITERAL"
>pg_stat_activity</TT
>, use this query:
</P><PRE
CLASS="PROGRAMLISTING"
>SELECT to_hex(EXTRACT(EPOCH FROM backend_start)::integer) || '.' ||
       to_hex(pid)
FROM pg_stat_activity;</PRE
><P>

</P
><DIV
CLASS="TIP"
><BLOCKQUOTE
CLASS="TIP"
><P
><B
>Tip: </B
>         If you set a nonempty value for <TT
CLASS="VARNAME"
>log_line_prefix</TT
>,
         you should usually make its last character be a space, to provide
         visual separation from the rest of the log line.  A punctuation
         character can be used too.
        </P
></BLOCKQUOTE
></DIV
><DIV
CLASS="TIP"
><BLOCKQUOTE
CLASS="TIP"
><P
><B
>Tip: </B
>         <SPAN
CLASS="APPLICATION"
>Syslog</SPAN
> produces its own
         time stamp and process ID information, so you probably do not want to
         include those escapes if you are logging to <SPAN
CLASS="APPLICATION"
>syslog</SPAN
>.
        </P
></BLOCKQUOTE
></DIV
></DD
><DT
><A
NAME="GUC-LOG-LOCK-WAITS"
></A
><TT
CLASS="VARNAME"
>log_lock_waits</TT
> (<TT
CLASS="TYPE"
>boolean</TT
>)</DT
><DD
><P
>        Controls whether a log message is produced when a session waits
        longer than <A
HREF="runtime-config-locks.html#GUC-DEADLOCK-TIMEOUT"
>deadlock_timeout</A
> to acquire a
        lock.  This is useful in determining if lock waits are causing
        poor performance.  The default is <TT
CLASS="LITERAL"
>off</TT
>.
        Only superusers can change this setting.
       </P
></DD
><DT
><A
NAME="GUC-LOG-STATEMENT"
></A
><TT
CLASS="VARNAME"
>log_statement</TT
> (<TT
CLASS="TYPE"
>enum</TT
>)</DT
><DD
><P
>        Controls which SQL statements are logged. Valid values are
        <TT
CLASS="LITERAL"
>none</TT
> (off), <TT
CLASS="LITERAL"
>ddl</TT
>, <TT
CLASS="LITERAL"
>mod</TT
>, and
        <TT
CLASS="LITERAL"
>all</TT
> (all statements). <TT
CLASS="LITERAL"
>ddl</TT
> logs all data definition
        statements, such as <TT
CLASS="COMMAND"
>CREATE</TT
>, <TT
CLASS="COMMAND"
>ALTER</TT
>, and
        <TT
CLASS="COMMAND"
>DROP</TT
> statements. <TT
CLASS="LITERAL"
>mod</TT
> logs all
        <TT
CLASS="LITERAL"
>ddl</TT
> statements, plus data-modifying statements
        such as <TT
CLASS="COMMAND"
>INSERT</TT
>,
        <TT
CLASS="COMMAND"
>UPDATE</TT
>, <TT
CLASS="COMMAND"
>DELETE</TT
>, <TT
CLASS="COMMAND"
>TRUNCATE</TT
>,
        and <TT
CLASS="COMMAND"
>COPY FROM</TT
>.
        <TT
CLASS="COMMAND"
>PREPARE</TT
>, <TT
CLASS="COMMAND"
>EXECUTE</TT
>, and
        <TT
CLASS="COMMAND"
>EXPLAIN ANALYZE</TT
> statements are also logged if their
        contained command is of an appropriate type.  For clients using
        extended query protocol, logging occurs when an Execute message
        is received, and values of the Bind parameters are included
        (with any embedded single-quote marks doubled).
       </P
><P
>        The default is <TT
CLASS="LITERAL"
>none</TT
>. Only superusers can change this
        setting.
       </P
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
>         Statements that contain simple syntax errors are not logged
         even by the <TT
CLASS="VARNAME"
>log_statement</TT
> = <TT
CLASS="LITERAL"
>all</TT
> setting,
         because the log message is emitted only after basic parsing has
         been done to determine the statement type.  In the case of extended
         query protocol, this setting likewise does not log statements that
         fail before the Execute phase (i.e., during parse analysis or
         planning).  Set <TT
CLASS="VARNAME"
>log_min_error_statement</TT
> to
         <TT
CLASS="LITERAL"
>ERROR</TT
> (or lower) to log such statements.
        </P
></BLOCKQUOTE
></DIV
></DD
><DT
><A
NAME="GUC-LOG-TEMP-FILES"
></A
><TT
CLASS="VARNAME"
>log_temp_files</TT
> (<TT
CLASS="TYPE"
>integer</TT
>)</DT
><DD
><P
>        Controls logging of temporary file names and sizes.
        Temporary files can be
        created for sorts, hashes, and temporary query results.
        A log entry is made for each temporary file when it is deleted.
        A value of zero logs all temporary file information, while positive
        values log only files whose size is greater than or equal to
        the specified number of kilobytes.  The
        default setting is -1, which disables such logging.
        Only superusers can change this setting.
       </P
></DD
><DT
><A
NAME="GUC-LOG-TIMEZONE"
></A
><TT
CLASS="VARNAME"
>log_timezone</TT
> (<TT
CLASS="TYPE"
>string</TT
>)</DT
><DD
><P
>        Sets the time zone used for timestamps written in the server log.
        Unlike <A
HREF="runtime-config-client.html#GUC-TIMEZONE"
>TimeZone</A
>, this value is cluster-wide,
        so that all sessions will report timestamps consistently.
        The built-in default is <TT
CLASS="LITERAL"
>GMT</TT
>, but that is typically
        overridden in <TT
CLASS="FILENAME"
>postgresql.conf</TT
>; <SPAN
CLASS="APPLICATION"
>initdb</SPAN
>
        will install a setting there corresponding to its system environment.
        See <A
HREF="datatype-datetime.html#DATATYPE-TIMEZONES"
>Section 8.5.3</A
> for more information.
        This parameter can only be set in the <TT
CLASS="FILENAME"
>postgresql.conf</TT
>
        file or on the server command line.
       </P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="RUNTIME-CONFIG-LOGGING-CSVLOG"
>18.8.4. Using CSV-Format Log Output</A
></H2
><P
>        Including <TT
CLASS="LITERAL"
>csvlog</TT
> in the <TT
CLASS="VARNAME"
>log_destination</TT
> list
        provides a convenient way to import log files into a database table.
        This option emits log lines in comma-separated-values
        (<ACRONYM
CLASS="ACRONYM"
>CSV</ACRONYM
>) format,
        with these columns:
        time stamp with milliseconds,
        user name,
        database name,
        process ID,
        client host:port number,
        session ID,
        per-session line number,
        command tag,
        session start time,
        virtual transaction ID,
        regular transaction ID,
        error severity,
        SQLSTATE code,
        error message,
        error message detail,
        hint,
        internal query that led to the error (if any),
        character count of the error position therein,
        error context,
        user query that led to the error (if any and enabled by
        <TT
CLASS="VARNAME"
>log_min_error_statement</TT
>),
        character count of the error position therein,
        location of the error in the PostgreSQL source code
        (if <TT
CLASS="VARNAME"
>log_error_verbosity</TT
> is set to <TT
CLASS="LITERAL"
>verbose</TT
>),
        and application name.
        Here is a sample table definition for storing CSV-format log output:

</P><PRE
CLASS="PROGRAMLISTING"
>CREATE TABLE postgres_log
(
  log_time timestamp(3) with time zone,
  user_name text,
  database_name text,
  process_id integer,
  connection_from text,
  session_id text,
  session_line_num bigint,
  command_tag text,
  session_start_time timestamp with time zone,
  virtual_transaction_id text,
  transaction_id bigint,
  error_severity text,
  sql_state_code text,
  message text,
  detail text,
  hint text,
  internal_query text,
  internal_query_pos integer,
  context text,
  query text,
  query_pos integer,
  location text,
  application_name text,
  PRIMARY KEY (session_id, session_line_num)
);</PRE
><P>
       </P
><P
>        To import a log file into this table, use the <TT
CLASS="COMMAND"
>COPY FROM</TT
>
        command:

</P><PRE
CLASS="PROGRAMLISTING"
>COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;</PRE
><P>
       </P
><P
>       There are a few things you need to do to simplify importing CSV log
       files:

<P
></P
></P><OL
TYPE="1"
><LI
><P
>            Set <TT
CLASS="VARNAME"
>log_filename</TT
> and
            <TT
CLASS="VARNAME"
>log_rotation_age</TT
> to provide a consistent,
            predictable naming scheme for your log files.  This lets you
            predict what the file name will be and know when an individual log
            file is complete and therefore ready to be imported.
         </P
></LI
><LI
><P
>            Set <TT
CLASS="VARNAME"
>log_rotation_size</TT
> to 0 to disable
            size-based log rotation, as it makes the log file name difficult
            to predict.
           </P
></LI
><LI
><P
>           Set <TT
CLASS="VARNAME"
>log_truncate_on_rotation</TT
> to <TT
CLASS="LITERAL"
>on</TT
> so
           that old log data isn't mixed with the new in the same file.
          </P
></LI
><LI
><P
>           The table definition above includes a primary key specification.
           This is useful to protect against accidentally importing the same
           information twice.  The <TT
CLASS="COMMAND"
>COPY</TT
> command commits all of the
           data it imports at one time, so any error will cause the entire
           import to fail.  If you import a partial log file and later import
           the file again when it is complete, the primary key violation will
           cause the import to fail.  Wait until the log is complete and
           closed before importing.  This procedure will also protect against
           accidentally importing a partial line that hasn't been completely
           written, which would also cause <TT
CLASS="COMMAND"
>COPY</TT
> to fail.
          </P
></LI
></OL
><P>
      </P
></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="runtime-config-query.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="runtime-config-statistics.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Query Planning</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="runtime-config.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Run-time Statistics</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