Runbook
PostgreSQL transaction logs causing disk space issues.
Back to Runbooks
Overview
This incident type pertains to an issue related to PostgreSQL transaction logs. The problem occurs when the transaction logs start filling up rapidly, leading to disk space issues. The growth of transaction logs is a normal occurrence, but it needs to be managed efficiently to prevent disk space problems. If the transaction logs are not managed properly, it can cause issues with the database's performance, and in some cases, can even crash the database. Therefore, it's important to monitor transaction logs growth and implement appropriate measures to manage it.
Parameters
Debug
Check disk space usage
Check PostgreSQL log file location
List all PostgreSQL log files
Check the size of the largest PostgreSQL log file
Check the current size of the PostgreSQL transaction log
Check the transaction log growth rate
Large transactions: If the database is handling large transactions, it can quickly fill up the transaction logs and cause disk space issues. This can happen if the database is used for data-intensive applications.
Repair
Check the PostgreSQL configuration parameters related to transaction logs, such as log_rotation_age, log_rotation_size, etc., and adjust them accordingly to manage the growth of transaction logs.
Purge old transaction logs periodically to free up disk space. This can be done manually or through an automated script.
Learn more
Related Runbooks
Check out these related runbooks to help you debug and resolve similar issues.