Set the followings settings in /etc/postgresql/15/main/postgresql.conf:"Error Reporting and Logging"<ul><li>logging_collector = on</li><li>log_min_duration_statement = 1s</li><li>log_lock_waits = on</li></ul>"Run-time Statistics"<ul><li>track_activity_query_size = 8192</li></ul>

Enable slow query log

<ol><li>Download the log files on your computer. The default location is <code>/var/lib/postgresql/15/main/log/</code>.</li><li>Install <a href="https://pgbadger.darold.net/">pgBadger</a></li><li>Analyze the logs: <code>pgbadger -o stats.html --prefix '%m \[%p\] %q%u@%d' /dir\_with\_logs/\*.log</code></li><li>Open the HTML output file in your browser to review the results</li></ol>

Analyze slow query log

computerscience

Computer Science

PostgreSQL supports several methods for logging server messages, including stderr , csvlog , jsonlog , and syslog . On Windows, eventlog is also supported. Set this parameter to a list of desired log destinations separated by commas. The default is to log to stderr only. This parameter can only be set in the <code>postgresql.conf </code>file or on the server command line.

If csvlog is included in <code>log_destination </code>, log entries are output in “comma separated value ” (<acronym>CSV </acronym>) format, which is convenient for loading logs into programs. See <a href="https://www.postgresql.org/docs/current/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-CSVLOG">Section 20.8.4 </a>for details. <a href="https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOGGING-COLLECTOR">logging_collector </a>must be enabled to generate CSV-format log output.

If jsonlog is included in <code>log_destination </code>, log entries are output in <acronym>JSON </acronym>format, which is convenient for loading logs into programs. See <a href="https://www.postgresql.org/docs/current/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-JSONLOG">Section 20.8.5 </a>for details. <a href="https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOGGING-COLLECTOR">logging_collector </a>must be enabled to generate JSON-format log output.

When either stderr , csvlog or jsonlog are included, the file <code>current_logfiles </code>is created to record the location of the log file(s) currently in use by the logging collector and the associated logging destination. This provides a convenient way to find the logs currently in use by the instance. Here is an example of this file's content:

<code>current_logfiles </code>is recreated when a new log file is created as an effect of rotation, and when <code>log_destination </code>is reloaded. It is removed when none of stderr , csvlog or jsonlog are included in <code>log_destination </code>, and when the logging collector is disabled.

On most Unix systems, you will need to alter the configuration of your system's syslog daemon in order to make use of the syslog option for <code>log_destination </code>. PostgreSQL can log to syslog facilities <code>LOCAL0 </code>through <code>LOCAL7 </code>(see <a href="https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-SYSLOG-FACILITY">syslog_facility </a>), but the default syslog configuration on most platforms will discard all such messages. You will need to add something like:

to the syslog daemon's configuration file to make it work.

On Windows, when you use the <code>eventlog </code>option for <code>log_destination </code>, 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="https://www.postgresql.org/docs/current/event-log-registration.html">Section 19.12 </a>for details.

This parameter enables the logging collector , which is a background process that captures log messages sent to stderr and redirects them into log files. This approach is often more useful than logging to syslog , since some types of messages might not appear in syslog output. (One common example is dynamic-linker failure messages; another is error messages produced by scripts such as <code>archive_command </code>.) This parameter can only be set at server start.

It is possible to log to stderr without using the logging collector; the log messages will just go to wherever the server's stderr 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.

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, syslog 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.

When <code>logging_collector </code>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 <code>postgresql.conf </code>file or on the server command line. The default is <code>log </code>.

When <code>logging_collector </code>is enabled, this parameter sets the file names of the created log files. The value is treated as a <code>strftime </code>pattern, so <code>% </code>-escapes can be used to specify time-varying file names. (Note that if there are any time-zone-dependent <code>% </code>-escapes, the computation is done in the zone specified by <a href="https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-TIMEZONE">log_timezone </a>.) The supported <code>% </code>-escapes are similar to those listed in the Open Group's <a href="https://pubs.opengroup.org/onlinepubs/009695399/functions/strftime.html">strftime </a>specification. Note that the system's <code>strftime </code>is not used directly, so platform-specific (nonstandard) extensions do not work. The default is <code>postgresql-%Y-%m-%d_%H%M%S.log </code>.

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 <code>% </code>escapes were present, PostgreSQL would append the epoch of the new log file's creation time, but this is no longer the case.

If CSV-format output is enabled in <code>log_destination </code>, <code>.csv </code>will be appended to the timestamped log file name to create the file name for CSV-format output. (If <code>log_filename </code>ends in <code>.log </code>, the suffix is replaced instead.)

If JSON-format output is enabled in <code>log_destination </code>, <code>.json </code>will be appended to the timestamped log file name to create the file name for JSON-format output. (If <code>log_filename </code>ends in <code>.log </code>, the suffix is replaced instead.)

This parameter can only be set in the <code>postgresql.conf </code>file or on the server command line.

On Unix systems this parameter sets the permissions for log files when <code>logging_collector </code>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>chmod </code>and <code>umask </code>system calls. (To use the customary octal format the number must start with a <code>0 </code>(zero).)

The default permissions are <code>0600 </code>, meaning only the server owner can read or write the log files. The other commonly useful setting is <code>0640 </code>, 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="https://www.postgresql.org/docs/current/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.

When <code>logging_collector </code>is enabled, this parameter determines the maximum amount of time to use an individual log file, after which a new log file will be created. If this value is specified without units, it is taken as minutes. The default is 24 hours. Set to zero to disable time-based creation of new log files. This parameter can only be set in the <code>postgresql.conf </code>file or on the server command line.

When <code>logging_collector </code>is enabled, this parameter determines the maximum size of an individual log file. After this amount of data has been emitted into a log file, a new log file will be created. If this value is specified without units, it is taken as kilobytes. The default is 10 megabytes. Set to zero to disable size-based creation of new log files. This parameter can only be set in the <code>postgresql.conf </code>file or on the server command line.

When <code>logging_collector </code>is enabled, this parameter will cause PostgreSQL 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 <code>log_filename </code>like <code>postgresql-%H.log </code>would result in generating twenty-four hourly log files and then cyclically overwriting them. This parameter can only be set in the <code>postgresql.conf </code>file or on the server command line.

Example: To keep 7 days of logs, one log file per day named <code>server_log.Mon </code>, <code>server_log.Tue </code>, etc., and automatically overwrite last week's log with this week's log, set <code>log_filename </code>to <code>server_log.%a </code>, <code>log_truncate_on_rotation </code>to <code>on </code>, and <code>log_rotation_age </code>to <code>1440 </code>.

Example: To keep 24 hours of logs, one log file per hour, but also rotate sooner if the log file size exceeds 1GB, set <code>log_filename </code>to <code>server_log.%H%M </code>, <code>log_truncate_on_rotation </code>to <code>on </code>, <code>log_rotation_age </code>to <code>60 </code>, and <code>log_rotation_size </code>to <code>1000000 </code>. Including <code>%M </code>in <code>log_filename </code>allows any size-driven rotations that might occur to select a file name different from the hour's initial file name.

When logging to syslog is enabled, this parameter determines the syslog “facility ” to be used. You can choose from <code>LOCAL0 </code>, <code>LOCAL1 </code>, <code>LOCAL2 </code>, <code>LOCAL3 </code>, <code>LOCAL4 </code>, <code>LOCAL5 </code>, <code>LOCAL6 </code>, <code>LOCAL7 </code>; the default is <code>LOCAL0 </code>. See also the documentation of your system's syslog daemon. This parameter can only be set in the <code>postgresql.conf </code>file or on the server command line.

When logging to syslog is enabled, this parameter determines the program name used to identify PostgreSQL messages in syslog logs. The default is <code>postgres </code>. This parameter can only be set in the <code>postgresql.conf </code>file or on the server command line.

When logging to syslog and this is on (the default), then each message will be prefixed by an increasing sequence number (such as <code>[2] </code>). This circumvents the “--- last message repeated N times --- ” suppression that many syslog implementations perform by default. In more modern syslog implementations, repeated message suppression can be configured (for example, <code>$RepeatedMsgReduction </code>in rsyslog ), so this might not be necessary. Also, you could turn this off if you actually want to suppress repeated messages.

When logging to syslog is enabled, this parameter determines how messages are delivered to syslog. When on (the default), messages are split by lines, and long lines are split so that they will fit into 1024 bytes, which is a typical size limit for traditional syslog implementations. When off, PostgreSQL server log messages are delivered to the syslog service as is, and it is up to the syslog service to cope with the potentially bulky messages.

If syslog is ultimately logging to a text file, then the effect will be the same either way, and it is best to leave the setting on, since most syslog implementations either cannot handle large messages or would need to be specially configured to handle them. But if syslog is ultimately writing into some other medium, it might be necessary or more useful to keep messages logically together.

When logging to event log is enabled, this parameter determines the program name used to identify PostgreSQL messages in the log. The default is <code>PostgreSQL </code>. This parameter can only be set in the <code>postgresql.conf </code>file or on the server command line.

Controls which <a href="https://www.postgresql.org/docs/current/runtime-config-logging.html#RUNTIME-CONFIG-SEVERITY-LEVELS">message levels </a>are written to the server log. Valid values are <code>DEBUG5 </code>, <code>DEBUG4 </code>, <code>DEBUG3 </code>, <code>DEBUG2 </code>, <code>DEBUG1 </code>, <code>INFO </code>, <code>NOTICE </code>, <code>WARNING </code>, <code>ERROR </code>, <code>LOG </code>, <code>FATAL </code>, and <code>PANIC </code>. Each level includes all the levels that follow it. The later the level, the fewer messages are sent to the log. The default is <code>WARNING </code>. Note that <code>LOG </code>has a different rank here than in <a href="https://www.postgresql.org/docs/current/runtime-config-client.html#GUC-CLIENT-MIN-MESSAGES">client_min_messages </a>. Only superusers and users with the appropriate <code>SET </code>privilege can change this setting.

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 <a href="https://www.postgresql.org/docs/current/runtime-config-logging.html#RUNTIME-CONFIG-SEVERITY-LEVELS">severity </a>or higher. Valid values are <code>DEBUG5 </code>, <code>DEBUG4 </code>, <code>DEBUG3 </code>, <code>DEBUG2 </code>, <code>DEBUG1 </code>, <code>INFO </code>, <code>NOTICE </code>, <code>WARNING </code>, <code>ERROR </code>, <code>LOG </code>, <code>FATAL </code>, and <code>PANIC </code>. The default is <code>ERROR </code>, 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 <code>PANIC </code>. Only superusers and users with the appropriate <code>SET </code>privilege can change this setting.

Causes the duration of each completed statement to be logged if the statement ran for at least the specified amount of time. For example, if you set it to <code>250ms </code>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. If this value is specified without units, it is taken as milliseconds. Setting this to zero prints all statement durations. <code>-1 </code>(the default) disables logging statement durations. Only superusers and users with the appropriate <code>SET </code>privilege can change this setting.

This overrides <a href="https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-MIN-DURATION-SAMPLE">log_min_duration_sample </a>, meaning that queries with duration exceeding this setting are not subject to sampling and are always logged.

For clients using extended query protocol, durations of the Parse, Bind, and Execute steps are logged independently.

When using this option together with <a href="https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-STATEMENT">log_statement </a>, the text of statements that are logged because of <code>log_statement </code>will not be repeated in the duration log message. If you are not using syslog , it is recommended that you log the PID or session ID using <a href="https://www.postgresql.org/docs/current/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.

Allows sampling the duration of completed statements that ran for at least the specified amount of time. This produces the same kind of log entries as <a href="https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-MIN-DURATION-STATEMENT">log_min_duration_statement </a>, but only for a subset of the executed statements, with sample rate controlled by <a href="https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-STATEMENT-SAMPLE-RATE">log_statement_sample_rate </a>. For example, if you set it to <code>100ms </code>then all SQL statements that run 100ms or longer will be considered for sampling. Enabling this parameter can be helpful when the traffic is too high to log all queries. If this value is specified without units, it is taken as milliseconds. Setting this to zero samples all statement durations. <code>-1 </code>(the default) disables sampling statement durations. Only superusers and users with the appropriate <code>SET </code>privilege can change this setting.

This setting has lower priority than <code>log_min_duration_statement </code>, meaning that statements with durations exceeding <code>log_min_duration_statement </code>are not subject to sampling and are always logged.

Other notes for <code>log_min_duration_statement </code>apply also to this setting.

Determines the fraction of statements with duration exceeding <a href="https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-MIN-DURATION-SAMPLE">log_min_duration_sample </a>that will be logged. Sampling is stochastic, for example <code>0.5 </code>means there is statistically one chance in two that any given statement will be logged. The default is <code>1.0 </code>, meaning to log all sampled statements. Setting this to zero disables sampled statement-duration logging, the same as setting <code>log_min_duration_sample </code>to <code>-1 </code>. Only superusers and users with the appropriate <code>SET </code>privilege can change this setting.

Sets the fraction of transactions whose statements are all logged, in addition to statements logged for other reasons. It applies to each new transaction regardless of its statements' durations. Sampling is stochastic, for example <code>0.1 </code>means there is statistically one chance in ten that any given transaction will be logged. <code>log_transaction_sample_rate </code>can be helpful to construct a sample of transactions. The default is <code>0 </code>, meaning not to log statements from any additional transactions. Setting this to <code>1 </code>logs all statements of all transactions. Only superusers and users with the appropriate <code>SET </code>privilege can change this setting.

Like all statement-logging options, this option can add significant overhead.

Sets the amount of time after which the startup process will log a message about a long-running operation that is still in progress, as well as the interval between further progress messages for that operation. The default is 10 seconds. A setting of <code>0 </code>disables the feature. If this value is specified without units, it is taken as milliseconds. This setting is applied separately to each operation. This parameter can only be set in the <code>postgresql.conf </code>file or on the server command line.

For example, if syncing the data directory takes 25 seconds and thereafter resetting unlogged relations takes 8 seconds, and if this setting has the default value of 10 seconds, then a messages will be logged for syncing the data directory after it has been in progress for 10 seconds and again after it has been in progress for 20 seconds, but nothing will be logged for resetting unlogged relations.

<a href="https://www.postgresql.org/docs/current/runtime-config-logging.html#RUNTIME-CONFIG-SEVERITY-LEVELS">Table 20.2 </a>explains the message severity levels used by PostgreSQL . If logging output is sent to syslog or Windows' eventlog , the severity levels are translated as shown in the table.

Table 20.2. Message Severity Levels

The <code>application_name </code>can be any string of less than <code>NAMEDATALEN </code>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 <code>pg_stat_activity </code>view and included in CSV log entries. It can also be included in regular log entries via the <a href="https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-LINE-PREFIX">log_line_prefix </a>parameter. Only printable ASCII characters may be used in the <code>application_name </code>value. Other characters will be replaced with question marks (<code>? </code>).

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 <code>LOG </code>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="https://www.postgresql.org/docs/current/runtime-config-client.html#GUC-CLIENT-MIN-MESSAGES">client_min_messages </a>and/or <a href="https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-MIN-MESSAGES">log_min_messages </a>. These parameters are off by default.

When set, <code>debug_pretty_print </code>indents the messages produced by <code>debug_print_parse </code>, <code>debug_print_rewritten </code>, or <code>debug_print_plan </code>. This results in more readable but much longer output than the “compact ” format used when it is off. It is on by default.

Causes each action executed by autovacuum to be logged if it ran for at least the specified amount of time. Setting this to zero logs all autovacuum actions. <code>-1 </code>disables logging autovacuum actions. If this value is specified without units, it is taken as milliseconds. For example, if you set this to <code>250ms </code>then all automatic vacuums and analyzes that run 250ms or longer will be logged. In addition, when this parameter is set to any value other than <code>-1 </code>, a message will be logged if an autovacuum action is skipped due to a conflicting lock or a concurrently dropped relation. The default is <code>10min </code>. Enabling this parameter can be helpful in tracking autovacuum activity. This parameter can only be set in the <code>postgresql.conf </code>file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters.

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 <code>postgresql.conf </code>file or on the server command line. The default is on.

Causes each attempted connection to the server to be logged, as well as successful completion of both client authentication (if necessary) and authorization. Only superusers and users with the appropriate <code>SET </code>privilege can change this parameter at session start, and it cannot be changed at all within a session. The default is <code>off </code>.

Some client programs, like psql , attempt to connect twice while determining if a password is required, so duplicate “connection received ” messages do not necessarily indicate a problem.

Causes session terminations to be logged. The log output provides information similar to <code>log_connections </code>, plus the duration of the session. Only superusers and users with the appropriate <code>SET </code>privilege can change this parameter at session start, and it cannot be changed at all within a session. The default is <code>off </code>.

Causes the duration of every completed statement to be logged. The default is <code>off </code>. Only superusers and users with the appropriate <code>SET </code>privilege can change this setting.

The difference between enabling <code>log_duration </code>and setting <a href="https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-MIN-DURATION-STATEMENT">log_min_duration_statement </a>to zero is that exceeding <code>log_min_duration_statement </code>forces the text of the query to be logged, but this option doesn't. Thus, if <code>log_duration </code>is <code>on </code>and <code>log_min_duration_statement </code>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.

Controls the amount of detail written in the server log for each message that is logged. Valid values are <code>TERSE </code>, <code>DEFAULT </code>, and <code>VERBOSE </code>, each adding more fields to displayed messages. <code>TERSE </code>excludes the logging of <code>DETAIL </code>, <code>HINT </code>, <code>QUERY </code>, and <code>CONTEXT </code>error information. <code>VERBOSE </code>output includes the <code>SQLSTATE </code>error code (see also <a href="https://www.postgresql.org/docs/current/errcodes-appendix.html">Appendix A </a>) and the source code file name, function name, and line number that generated the error. Only superusers and users with the appropriate <code>SET </code>privilege can change this setting.

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 <code>postgresql.conf </code>file or on the server command line.

This is a <code>printf </code>-style string that is output at the beginning of each log line. <code>% </code>characters begin “escape sequences ” 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 will be treated as empty by background processes such as the main server process. Status information may be aligned either left or right by specifying a numeric literal after the % and before the option. A negative value will cause the status information to be padded on the right with spaces to give it a minimum width, whereas a positive value will pad on the left. Padding can be useful to aid human readability in log files.

This parameter can only be set in the <code>postgresql.conf </code>file or on the server command line. The default is <code>'%m [%p] ' </code>which logs a time stamp and the process ID.

The backend type corresponds to the column <code>backend_type </code>in the view <a href="https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-ACTIVITY-VIEW"><code>pg_stat_activity </code> </a>, but additional types can appear in the log that don't show in that view.

The <code>%c </code>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 <code>%c </code>can also be used as a space saving way of printing those items. For example, to generate the session identifier from <code>pg_stat_activity </code>, use this query:

If you set a nonempty value for <code>log_line_prefix </code>, 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.

Syslog produces its own time stamp and process ID information, so you probably do not want to include those escapes if you are logging to syslog .

The <code>%q </code>escape is useful when including information that is only available in session (backend) context like user or database name. For example:

The <code>%Q </code>escape always reports a zero identifier for lines output by <a href="https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-STATEMENT">log_statement </a>because <code>log_statement </code>generates output before an identifier can be calculated, including invalid statements for which an identifier cannot be calculated.

Controls whether a log message is produced when a session waits longer than <a href="https://www.postgresql.org/docs/current/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 <code>off </code>. Only superusers and users with the appropriate <code>SET </code>privilege can change this setting.

Controls whether a log message is produced when the startup process waits longer than <code>deadlock_timeout </code>for recovery conflicts. This is useful in determining if recovery conflicts prevent the recovery from applying WAL.

The default is <code>off </code>. This parameter can only be set in the <code>postgresql.conf </code>file or on the server command line.

If greater than zero, each bind parameter value logged with a non-error statement-logging message is trimmed to this many bytes. Zero disables logging of bind parameters for non-error statement logs. <code>-1 </code>(the default) allows bind parameters to be logged in full. If this value is specified without units, it is taken as bytes. Only superusers and users with the appropriate <code>SET </code>privilege can change this setting.

This setting only affects log messages printed as a result of <a href="https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-STATEMENT">log_statement </a>, <a href="https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-LOG-DURATION">log_duration </a>, and related settings. Non-zero values of this setting add some overhead, particularly if parameters are sent in binary form, since then conversion to text is required.

If greater than zero, each bind parameter value reported in error messages is trimmed to this many bytes. Zero (the default) disables including bind parameters in error messages. <code>-1 </code>allows bind parameters to be printed in full. If this value is specified without units, it is taken as bytes.

Non-zero values of this setting add overhead, as PostgreSQL will need to store textual representations of parameter values in memory at the start of each statement, whether or not an error eventually occurs. The overhead is greater when bind parameters are sent in binary form than when they are sent as text, since the former case requires data conversion while the latter only requires copying the string.

Controls which SQL statements are logged. Valid values are <code>none </code>(off), <code>ddl </code>, <code>mod </code>, and <code>all </code>(all statements). <code>ddl </code>logs all data definition statements, such as <code>CREATE </code>, <code>ALTER </code>, and <code>DROP </code>statements. <code>mod </code>logs all <code>ddl </code>statements, plus data-modifying statements such as <code>INSERT </code>, <code>UPDATE </code>, <code>DELETE </code>, <code>TRUNCATE </code>, and <code>COPY FROM </code>. <code>PREPARE </code>, <code>EXECUTE </code>, and <code>EXPLAIN ANALYZE </code>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).

The default is <code>none </code>. Only superusers and users with the appropriate <code>SET </code>privilege can change this setting.

Statements that contain simple syntax errors are not logged even by the <code>log_statement </code>= <code>all </code>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 <code>log_min_error_statement </code>to <code>ERROR </code>(or lower) to log such statements.

Logged statements might reveal sensitive data and even contain plaintext passwords.

Causes each replication command to be logged in the server log. See <a href="https://www.postgresql.org/docs/current/protocol-replication.html">Section 55.4 </a>for more information about replication command. The default value is <code>off </code>. Only superusers and users with the appropriate <code>SET </code>privilege can change this setting.

Controls logging of temporary file names and sizes. Temporary files can be created for sorts, hashes, and temporary query results. If enabled by this setting, a log entry is emitted 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 amount of data. If this value is specified without units, it is taken as kilobytes. The default setting is -1, which disables such logging. Only superusers and users with the appropriate <code>SET </code>privilege can change this setting.

Sets the time zone used for timestamps written in the server log. Unlike <a href="https://www.postgresql.org/docs/current/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 <code>GMT </code>, but that is typically overridden in <code>postgresql.conf </code>; initdb will install a setting there corresponding to its system environment. See <a href="https://www.postgresql.org/docs/current/datatype-datetime.html#DATATYPE-TIMEZONES">Section 8.5.3 </a>for more information. This parameter can only be set in the <code>postgresql.conf </code>file or on the server command line.

Including <code>csvlog </code>in the <code>log_destination </code>list provides a convenient way to import log files into a database table. This option emits log lines in comma-separated-values (<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 <code>log_min_error_statement </code>), character count of the error position therein, location of the error in the PostgreSQL source code (if <code>log_error_verbosity </code>is set to <code>verbose </code>), application name, backend type, process ID of parallel group leader, and query id. Here is a sample table definition for storing CSV-format log output:

PostgreSQL - How to Configure Slow Query Log

Enable slow query log

Analyze slow query log

Other curated ideas on this topic: