Database Reference
In-Depth Information
How it works...
The server log is just a file that records messages from the server. Each message has a
severity level, the most typical one being LOG, though there are others, as shown in the
following table:
PostgreSQL
Severity
Meaning
Syslog Severity Windows eventlog
DEBUG 1
through
DEBUG 5
Internal diagnostics
DEBUG
INFORMATION
INFO
Command output for user
INFO
INFORMATION
NOTICE
Helpful information
NOTICE
INFORMATION
WARNING
Warns of likely problems
NOTICE
WARNING
ERROR
Current command aborted
WARNING
ERROR
LOG
For sysadmins
INFO
INFORMATION
FATAL
Event that disconnects one session only ERR
ERROR
PANIC
Event that crashes server
CRIT
ERROR
Watch for FATALs and PANICs. They shouldn't happen in most cases during normal server
operation, apart from certain cases related to Replication, so check out that chapter also.
You can adjust the number of messages that appear in the log by changing the
log_min_
messages
server parameter. You can also change the amount of information that is displayed
for each event by changing the
log_error_verbosity
. If the messages are sent to a
standard log file, then each line in the log will have a prefix of useful information that can also
be controlled by the system administrator, named
log_line_prefix
. Locate the database's
system identifier???
Each database server has a system identifier assigned when the database is initialized
(created). The server identifier remains the same if the server is backed up, cloned, and so on.
Many actions on the server are keyed to the system identifier, and you may be asked
to provide this information when you report a fault.
Getting ready
Connect as the postgres OS user, or another user with execute privileges on the server software.
