🔭 Want to centralize and monitor your PostgreSQL logs?
Head over to Logtail and start ingesting your logs in 5 minutes.
This tutorial shows you how to configure and view different PostgreSQL logs. PostgreSQL is an open-source relational database based on SQL (Structured Query Language). PostgreSQL offers a complex logging daemon called logging collector. In general, the database is the basis of almost every backend, and administrators want to log this service.
In this tutorial, you will do the following:
- You will install the PostgreSQL server and view syslog records related to this service. Next, you will view the database custom log.
- You will connect to the PostgreSQL server and view metadata about the logging collector. You will enable this daemon.
- You will understand the most important PostgreSQL logging configuration setting. You will view, edit and reload server configuration.
- You will simulate some slow query and check this incident in the new log.
Prerequisites
You will need:
- Ubuntu 20.04 distribution including the non-root user with
sudoaccess. - Basic knowledge of SQL languages (understanding of simple select query statement).
- Understanding of systemd and systemctl. All basics are covered in our How to Control Systemd with Systemctl tutorial.
- You should know the principle of rotation logs. You can consult our How to Control Journald with Journalctl tutorial.
Step 1 — Installing Server and Viewing Syslog Records
The PostgreSQL server is maintained by the command-line program psql. This
program access the interactive terminal for accessing the database. The process
of starting, running or stopping the PostgreSQL server is logged into syslog.
These syslog records don't include any information about SQL queries. It is
useful for the analysis of the server.
First of all, let's install the PostgreSQL server. Ubuntu 20.04 allows to
install the PostgreSQL from default packages with the apt install
(installation requires sudo privilege):
$ sudo apt update
$ sudo apt install postgresql
The first command will update Ubuntu repositories, and the second will download and install required packages for the PostgreSQL server.
Now, the server is installed and started. The process of server starting is
recoded in syslog. You can view all syslog records related to the PostgreSQL
with journalctl:
$ journalctl -u postgresql
The option -u defines to show only syslog records related to service
postgresql. You'll see the program's output appear on the screen:
Output
-- Logs begin at Thu 2021-03-25 18:44:20 CET, end at Sun 2021-05-09 21:30:01 CEST. --
May 09 21:29:47 alice systemd[1]: Starting PostgreSQL RDBMS...
May 09 21:29:47 alice systemd[1]: Finished PostgreSQL RDBMS.
The output shows the records about the first server start.
Step 2 — Viewing the Custom Server Log
Except for syslog records, PostgreSQL maintains its own log. This log includes
much more detailed information than general syslog records, and it is widely
adjustable. The log is stored in the default log directory for Linux systems
(/var/log).
If you installed the PostgreSQL server, you can list the directory /var/log
and find a new subdirectory postgresql with ls:
$ ls /var/log/
You'll see the program's output appear on the screen:
Output
alternatives.log bootstrap.log kern.log.4.gz
alternatives.log.1 btmp lastlog
alternatives.log.2.gz btmp.1 letsencrypt
alternatives.log.3.gz cups my-custom-app
apache2 dist-upgrade postgresql
apport.log dmesg openvpn
apport.log.1 dmesg.0 private
apport.log.2.gz dmesg.1.gz speech-dispatcher
apport.log.3.gz dmesg.2.gz syslog
apport.log.4.gz dmesg.3.gz syslog.1
apport.log.5.gz dmesg.4.gz syslog.2.gz
apport.log.6.gz dpkg.log syslog.3.gz
apport.log.7.gz dpkg.log.1 syslog.4.gz
apt dpkg.log.2.gz syslog.5.gz
auth.log dpkg.log.3.gz syslog.6.gz
auth.log.1 faillog syslog.7.gz
auth.log.2.gz fontconfig.log teamviewer15
auth.log.3.gz gdm3 test.log
auth.log.4.gz gpu-manager.log ubuntu-advantage.log
boot.log gpu-manager-switch.log unattended-upgrades
boot.log.1 hp wtmp
boot.log.2 installer wtmp.1
boot.log.3 journal Xorg.0.log
boot.log.4 kern.log Xorg.0.log.old
boot.log.5 kern.log.1 Xorg.1.log
boot.log.6 kern.log.2.gz Xorg.1.log.old
boot.log.7 kern.log.3.gz
The output shows also directory postgresql. This directory contains by default
single log postgresql-12-main.log. Let's view the content of this file with
cat:
cat /var/log/postgresql/postgresql-12-main.log
You'll see the program's output appear on the screen:
Output
2021-05-08 19:47:57.996 CEST [349090] LOG: starting PostgreSQL 12.6 (Ubuntu 12.6-0ubuntu0.20.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, 64-bit
2021-05-08 19:47:57.997 CEST [349090] LOG: listening on IPv4 address "127.0.0.1", port 5432
2021-05-08 19:47:58.001 CEST [349090] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2021-05-08 19:47:58.022 CEST [349091] LOG: database system was shut down at 2021-05-08 19:47:56 CEST
2021-05-08 19:47:58.034 CEST [349090] LOG: database system is ready to accept connections
...
The output shows that the file stores plain text records about the PostgreSQL server initialisation, and running. You can see that these records are much more detailed than the syslog records.
Step 3 — Connecting to Server and Checking Log Collector
By default, the PostgreSQL logs are maintained by the syslog daemon. However, the database includes a dedicated logging collector (daemon independent of syslog) that offers a more advanced log configuration specialized for logging the database.
First of all, let's connect to the PostgreSQL server and check the logging
configuration. You can connect to the PostgreSQL server as a user postgres
(this user account is created by default within installation):
$ sudo -u postgres psql
The command requires sudo because you are changing the user role. You will be
redirected to PostgreSQL interactive terminal. Now, you can view system
variables related to the logging configuration.
You can view the status of the log collector by executing the command show:
postgres=# show logging_collector;
The command show displays the value of the system variable
logging_collector. You will see the following output:
Output
logging_collector
-------------------
off
As you can see, the PostgreSQL log collector is by default disabled. We will
enable it in the next step. Now, let's disconnect from the server by executing
the exit command:
postgres=# exit;
You will be redirected back to the terminal.
Step 4 — Enabling the PostgreSQL Log Collector
The PostgreSQL server includes various system variables that specify the
configuration of logging. All these variables are stored in the configuration
file postgresql.conf. This file is by default stored in the directory
/etc/postgresql/12/main/. The following list explains the meaning of the most
important server log variables:
logging_collector: We already know this variable from the previous step. However, for completeness, it is included in this list because it is one of the most important log configuration settings.log_destination: Sets the destination for server log output.log_directory: It determines the directory in which log files will be created.log_filename: It sets the file names of the created log files.log_line_prefix: Each log record includes, besides the message itself, a header prefix with important metadata (for example, timestamp, user, process id, and others). You can specify the header fields in this variable.log_hostname: If this variable is disabled then the log will record only the IP address of clients. If it is enabled then the log will map the IP address to hostname. However, you should keep in mind that DNS translation cost resources.log_timezone: The variable holds geographical location. It converts the timestamp into the relevant local format.log_connections: If you enable this variable then the log will record all authorized connections, or attempts to the server. It could be beneficial for security auditing, but it could be also a heavy load for the server if you have thousands of clients.log_disconnections: This variable is complementary to the previous one. By enabling it, you set up to log all authorised disconnection. Typically, you want to enable only one of these two variables.log_statement: The variable determines which SQL statement will be logged.log_duration: It is the boolean variable. If it is enabled then all SQL statements will be recorded together with their duration. This setting could decrease database performance. However, it could be beneficial for determining slow queries.log_min_duration_statement: The variable is extension of previous setting. It specifies the minimal duration of SQL statement in a millisecond that will be logged.log_rotation_age: The integer value determines the maximal time period of minutes until log rotation.log_rotation_size: The value set the maximal size of the log file in kilobytes. If the log reaches this value, it will be rotated.
Each of these variables can be viewed through the psql terminal. If you want
to view them, you can follow the previous step, where we already view the
variable logging_collector. For further information about configuration
variables see the official
documentation.
Enabling Log Collector
You can enable log collector daemon by editing the postgresql.conf (sudo
required):
$ sudo nano /etc/postgresql/12/main/postgresql.conf
The file contains the following lines that hold configuration variables
logging_collector and log_destination (by default commented out):
# - Where to Log -
#log_destination = 'stderr' # Valid values are combinations of
# stderr, csvlog, syslog, and eventlog,
# depending on platform. csvlog
# requires logging_collector to be on.
# This is used when logging to stderr:
#logging_collector = off # Enable capturing of stderr and csvlog
# into log files. Required to be on for
# csvlogs.
# (change requires restart)
Uncomment both variables, set logging_collector to on and log_destination
to stderr:
# - Where to Log -
log_destination = 'stderr' # Valid values are combinations of
# stderr, csvlog, syslog, and eventlog,
# depending on platform. csvlog
# requires logging_collector to be on.
# This is used when logging to stderr:
logging_collector = on # Enable capturing of stderr and csvlog
# into log files. Required to be on for
# csvlogs.
# (change requires restart)
Now, you can save the file. You set up log destination to stderr because log
collector read input from there. The configuration is now changed but the log
daemon is not activated yet. If you want immediately apply the new configuration
rules then you must restart the PostgreSQL server with systemctl (sudo
required):
$ sudo systemctl restart postgresql.service
Now, the PostgreSQL server reloads the configuration and enables a log
collector. If you want to change any variable in the file postgresql.conf and
immediately apply changes, you must restart the service.
Step 5 — Configuring Log Collector
Now, you will set up the variables described in the previous step. Keep in mind
that each organisation has unique logging requirements. This tutorial shows you
the possible setup, but you should configure values that match your use case.
All these variables are stored in the file
/etc/postgresql/12/main/postgresql.conf. If you want to change any of these
variables, then edit this file and restart the PostgreSQL server as we did in
the previous step.
Configuring Log Name, Directory and Rotation
The naming of logs becomes important if you manage logs from multiple
services and servers. The log files created by the log collector are named by
the regular expression determined in the variable log_filename. The name could
include a constant string but also a
formatted timestamp.
The default log name is postgresql-%Y-%m-%d_%H%M%S.log. The pattern
%Y-%m-%d_%H%M%S determines formatted timestamp:
%Y: The year as a decimal number including the century.%m: The month as a decimal number (range 01 to 12).%d: The day of the month as a decimal number (range 01 to 31).%H: The hour as a decimal number using a 24-hour clock (range 00 to 23).%M: The minute as a decimal number (range 00 to 59).%S: The second as a decimal number (range 00 to 60).
The created file could be named, for example, as
postgresql-2021-01-01_23:59:59:59.log.
The file-system directory of the log is determined by the variable
log_directory. You should keep in mind that Linux typically stores all logs
into the /var/log/ directory.
The log collector allows configuring log rotation. It is the same log
rotation principle as the syslog logrotate but this rotation is maintained by
PostgreSQL log controller daemon instead of syslog. If you do not know what is
log rotation, you can read How to Manage Logs with Logrotate on Ubuntu
20.04. The log rotation
is configured by following two values in the postgresql.conf:
log_rotation_age: If the value is set to 0 then the log rotation is disabled. The default value is 1 day, but this value depends on your use case. The integer without units refers to the number of seconds.log_rotation_size: If the value is set to 0 then the log rotation is disabled, otherwise the automatic log file rotation will occur after a specified number of kilobytes.
You can view all these variables in the postgresql.conf:
$ nano /etc/postgresql/12/main/postgresql.conf
The file contains the following lines that hold described configuration variables (by default commented out):
# These are only used if logging_collector is on:
#log_directory = 'log' # directory where log files are written,
# can be absolute or relative to PGDATA
#log_filename = 'postgresql-%Y-%m-%d_%H%M%S.log' # log file name pattern,
# can include strftime() escapes
#log_file_mode = 0600 # creation mode for log files,
# begin with 0 to use octal notation
#log_truncate_on_rotation = off # If on, an existing log file with the
# same name as the new log file will be
# truncated rather than appended to.
# But such truncation only occurs on
# time-driven rotation, not on restarts
# or size-driven rotation. Default is
# off, meaning append to existing files
# in all cases.
#log_rotation_age = 1d # Automatic rotation of logfiles will
# happen after that time. 0 disables.
#log_rotation_size = 10MB # Automatic rotation of logfiles will
# happen after that much log output.
# 0 disables.
Now, you can close the file. You can potentially edit these values, but in such
a case you need sudo access.
Configuring Log Structure
You can configure the structure of each log record by various configuration
variables. Firstly, let's set up a record header (information prefixed to
each log line). The record prefix structure is determined by the variable
log_line_prefix, which holds the printf style string. The following list
shows the most important escape characters:
%t: Timestamp without milliseconds (%mis with miliseconds). If you want to configure timestamp format to a specific local time then you can set up variablelog_timezoneto chosen geographical location. For exampleAmerica/New_York,Europe/Paris, or any other name from the IANA timezone database.%p: Process ID.%q: If it is non-session process then stop record at this point.%d: Name of database.%u: User name.%h: Remote hostname or IP address. By default, the IP address is recorded. You can set up DNS translation to hostname by enabling variablelog_hostnameto valueon. However, this setting is usually too expensive because it might impose a non-negligible performance penalty.%a: Application name.%l: Numbering the records in each session (every session start from number 1).
The log_line_prefix with value '%t [%p] %q%d@%u, %h, %a, %l ' will hold, for
example, following log record:
2021-05-15 08:21:27 CEST [527518] postgres@postgres, [local], psql, 3 STATEMENT: select pq_sleep(5);
Once again, you can view all these variables in the postgresql.conf:
$ nano /etc/postgresql/12/main/postgresql.conf
The file contains the following lines that hold described configuration variables:
#log_hostname = off
log_line_prefix = '%m [%p] %q%u@%d '
...
log_timezone = 'Europe/Vienna'
As you can see, the DNS translation to the hostname is by default disabled, the default log line prefix record timestamp with milliseconds, process, user and IP address, and the timezone are set to geographical location preset from OS.
Configuring Log Collector to Record Selected SQL Commands
You can configure which type of action will be logged with the log collector. There are two boolean variables that enable logging of the following database actions:
- Logs each attempt, or successful connection to the database. This is by
default disabled. You can enable it by setting the variable
log_connectionstoon. - Logs the duration of each completed SQL statement. By default it is
disabled. You can enable it by setting the variable
log_durationto the valueon. If you want to log only slow queries then you can set the minimum execution time above which all statements will be logged. The variablelog_min_duration_statementholds the minimal value as an integer in milliseconds.
Within the log_connections variable, there is also a log_disconnections
variable that logs successful disconnections from the database. A database
usually logs a large number of connection attempts, soo you want to enable just
one of them to save resources.
At last, you can set up which SQL statements are logged. This setting
determines variable log_statement, which can hold one of the following four
values:
none: The SQL statements logging is disabled.ddl: The log collector will log all data definition statements (CREATE,ALTER, andDROP).mod: Same as theddlplus data-modifying statements (UPDATE,INSERT,DELETEand others).all: All SQL statements are recorded.
Once again, you can view all these values in the postgresql.conf:
$ nano /etc/postgresql/12/main/postgresql.conf
The file contains the following lines that hold described configuration variables:
#log_min_duration_statement = -1 # -1 is disabled, 0 logs all statements
# and their durations, > 0 logs only
# statements running at least this number
# of milliseconds
...
#log_connections = off
#log_disconnections = off
#log_duration = off
...
#log_statement = 'none' # none, ddl, mod, all
As you can see, by default, all these database actions are not logged.
Step 6 — Viewing Collector Logs
If you set up all described variables in postgresql.conf and restart the
server then you can view the content of the new logs.
For demonstration, we will use following postgresql.conf configuration:
log_destination = 'stderr'
logging_collector = on
log_directory = '/var/log/postgresql'
log_filename = 'postgresql-%Y-%m-%d_%H%M%S.log'
log_rotation_age = 1d
log_rotation_size = 10MB
log_min_duration_statement = 250
log_connections = on
log_duration = on
log_hostname = on
log_line_prefix = '%t [%p] %q%d@%u, %h, %a, %l '
log_statement = 'all'
log_timezone = 'Europe/Vienna'
Executing SQL Statement
First of all, let's connect to the PostgreSQL server and execute some SQL
statement. You can connect to the PostgreSQL server as a user postgres (sudo
required):
$ sudo -u postgres psql
You will be redirected to PostgreSQL interactive terminal. Let's execute some SQL statement that will be logged:
postgres=# select pg_sleep(1);
The command select call function pg_sleep() that fall asleep for 1 second
(our configuration records every statement longer than 250ms).
Now, let's disconnect from the server by executing the exit command:
postgres=# exit;
You will be redirected back to the terminal.
Viewing Record of Executed SQL Statement in the Log
Now, let's view the new collector log that holds a record of SQL statement
executions. Our configuration specifies log directory to /var/log/postgresql.
Let's list the content of this directory with ls:
$ ls /var/log/postgresql
You'll see the program's output appear on the screen:
Output
postgresql-12-main.log postgresql-2021-05-15_115637.log
The output shows, within the default log file postgresql-12-main.log, a new
log postgresql-2021-05-15_115637.log. You can validate that the name of the
log match with the configuration string in variable log_filename.
Let's view the content of this log with a cat (the sudo is required because
this file is maintained by the system):
$ sudo cat /var/log/postgresql/postgresql-2021-05-15_115637.log
You'll see the program's output appear on the screen:
Output
2021-05-15 12:03:50 CEST [535071] LOG: database system was shut down at 2021-05-15 12:03:50 CEST
2021-05-15 12:03:51 CEST [535069] LOG: database system is ready to accept connections
2021-05-15 12:03:51 CEST [535078] [unknown]@[unknown], [local], [unknown], 1 LOG: connection received: host=[local]
2021-05-15 12:03:52 CEST [535081] [unknown]@[unknown], [local], [unknown], 1 LOG: connection received: host=[local]
2021-05-15 12:03:52 CEST [535081] template1@postgres, [local], [unknown], 2 LOG: connection authorized: user=postgres database=template1 application_name=psql
2021-05-15 12:03:52 CEST [535081] template1@postgres, [local], psql, 3 LOG: statement:
2021-05-15 12:03:52 CEST [535081] template1@postgres, [local], psql, 4 LOG: duration: 0.072 ms
2021-05-15 12:03:52 CEST [535084] [unknown]@[unknown], [local], [unknown], 1 LOG: connection received: host=[local]
2021-05-15 12:03:52 CEST [535084] template1@postgres, [local], [unknown], 2 LOG: connection authorized: user=postgres database=template1 application_name=psql
2021-05-15 12:03:52 CEST [535084] template1@postgres, [local], psql, 3 LOG: statement:
2021-05-15 12:03:52 CEST [535084] template1@postgres, [local], psql, 4 LOG: duration: 0.069 ms
2021-05-15 12:03:53 CEST [535087] [unknown]@[unknown], [local], [unknown], 1 LOG: connection received: host=[local]
2021-05-15 12:03:53 CEST [535087] template1@postgres, [local], [unknown], 2 LOG: connection authorized: user=postgres database=template1 application_name=psql
2021-05-15 12:03:53 CEST [535087] template1@postgres, [local], psql, 3 LOG: statement:
2021-05-15 12:03:53 CEST [535087] template1@postgres, [local], psql, 4 LOG: duration: 0.140 ms
2021-05-15 12:05:22 CEST [535250] [unknown]@[unknown], [local], [unknown], 1 LOG: connection received: host=[local]
2021-05-15 12:05:22 CEST [535250] postgres@postgres, [local], [unknown], 2 LOG: connection authorized: user=postgres database=postgres application_name=psql
2021-05-15 12:05:25 CEST [535250] postgres@postgres, [local], psql, 3 LOG: statement: select pg_sleep(1);
2021-05-15 12:05:26 CEST [535250] postgres@postgres, [local], psql, 4 LOG: duration: 1002.681 ms
The output shows all records in this log. First records refer to the startup of
the server. You can see that all records are in the format as specified in the
variable log_line_prefix. You can view the last three records that hold
information about the connection to the database through psql as a user
postgres and executing command select pg_sleep(1). The records include also
a time of SQL statement execution.
As you can see, the logging collector with this configuration generates a relatively huge amount of records in a short time. You should find the best configuration that matches your use case.
Conclusion
In this tutorial, you installed the PostgreSQL server. You viewed the syslog records related to this service and the database custom log. You viewed the log collector configuration. You understood the meaning of the most important settings in the configuration file. At last, you enabled, configured and viewed a logging collector.
Centralize all your logs into one place.
Analyze, correlate and filter logs with SQL.
Create actionable
dashboards.
dashboards.
Share and comment with built-in collaboration.
Got an article suggestion?
Let us know
Next article
How To Start Logging With MariaDB
Learn how to start logging with MariaDB and go from basics to best practices in no time.
→
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Centralize all your logs into one place.
Analyze, correlate and filter logs with SQL.
Create actionable
dashboards.
dashboards.
Share and comment with built-in collaboration.