Analiz için Günlük Kaydı Yapılandırması

Understanding how your PostgreSQL database performs is crucial for maintaining its health and speed. Logs are your database's diary, recording important events, errors, and even slow queries.

By configuring logging correctly, you gain deep insights into what's happening under the hood, making troubleshooting and performance analysis much easier.

PostgreSQL can send its log output to different places. The log_destination parameter in postgresql.conf controls this.

• stderr: Logs go to standard error (console).
• csvlog: Logs are written in a CSV format, great for programmatic analysis.
• syslog: Logs go to the system's logging facility.

For most users, stderr (captured by a collector) or csvlog are the most common and useful options.

If log_destination includes stderr, you'll want PostgreSQL to capture these logs into files. This is where logging_collector comes in.

When logging_collector is on, PostgreSQL starts a background process to capture stderr messages and redirect them to log files. You can specify the log_directory and log_filename.

Here's how to enable it:

To see every SQL command executed, you can set log_statement = 'all'. This is very verbose and can generate huge log files, so use it with caution and typically only for short-term debugging.

Let's say you run this query:

With log_statement = 'all', the previous query would appear in your logs. Other useful settings include:

• ddl: Logs all Data Definition Language (CREATE, ALTER, DROP).
• mod: Logs DDL and Data Manipulation Language (INSERT, UPDATE, DELETE).
• none: No statements are logged (default).

For general monitoring, ddl or mod can be a good balance, capturing schema changes and data modifications.

This is one of the most powerful logging parameters for performance analysis. log_min_duration_statement logs any statement that runs longer than the specified number of milliseconds.

Setting it to 0 logs all statements with their duration. Setting it to -1 (the default) disables it.

Example: To log queries slower than 200ms:

If log_min_duration_statement is set to 100 (100ms), a query like this would appear in your logs if it takes longer than 100ms to execute. This helps identify performance bottlenecks.

Tracking client activity can be vital for security and resource management. You can configure PostgreSQL to log when clients connect and disconnect.

• log_connections = on: Logs successful connection attempts.
• log_disconnections = on: Logs client disconnections, including session duration.

These settings provide valuable context about who is connecting, from where, and for how long.

The log_line_prefix parameter allows you to add useful information at the beginning of each log line. This makes logs much easier to parse and understand.

Common prefixes include timestamp, user, database, process ID, and client IP address. For example:

Which configuration parameter is used to log SQL statements that exceed a specific execution time, making it invaluable for identifying performance bottlenecks?

You've learned how to configure PostgreSQL logging for effective analysis and troubleshooting.

• We covered log_destination for output location.
• Enabled logging_collector to capture logs to files.
• Used log_statement for general query logging.
• Identified slow queries with the powerful log_min_duration_statement.
• Explored log_connections and log_line_prefix for context.

Proper logging is your first line of defense in understanding and optimizing your PostgreSQL database!