---
id: 4759558d-8b82-4184-bf00-7366eb05c71f
---

# PostgreSQL database reporting disk full errors.
---

This incident type refers to a problem with a PostgreSQL database where it is reporting disk full errors. This means that the database has reached its full capacity and cannot store any more data. This can cause issues with the performance of the database and may result in data loss if not addressed promptly.

### Parameters
```shell
export PATH_TO_POSTGRESQL_DATA_DIRECTORY="PLACEHOLDER"

export DATABASE_NAME="PLACEHOLDER"

export TABLE_NAME="PLACEHOLDER"

export BACKUP_DIRECTORY="PLACEHOLDER"

export HOST="PLACEHOLDER"

export USERNAME="PLACEHOLDER"

export CONDITION="PLACEHOLDER"
```

## Debug

### 1. Check the disk usage of the PostgreSQL data directory
```shell
df -h ${PATH_TO_POSTGRESQL_DATA_DIRECTORY}
```

### 2. Check the disk usage of the entire system to see if any other partitions are full
```shell
df -h
```

### 3. Check the size and usage of individual tables in the database
```shell
psql -d ${DATABASE_NAME} -c "SELECT pg_size_pretty(pg_total_relation_size('${TABLE_NAME}')) AS total_size;"
```

### 4. Check the size and usage of individual indexes in the database
```shell
psql -d ${DATABASE_NAME} -c "SELECT pg_size_pretty(pg_indexes_size('${TABLE_NAME}')) AS index_size;"
```

### 5. Check for any large and unnecessary files in the PostgreSQL data directory
```shell
find ${PATH_TO_POSTGRESQL_DATA_DIRECTORY} -type f -size +10M -exec ls -lh {} \;
```

### The disk where the PostgreSQL database is stored may have run out of storage space due to large database files or logs.
```shell
bash

#!/bin/bash



# check size of the PostgreSQL database files

du -hs ${PATH_TO_POSTGRESQL_DATA_DIRECTORY}



# check for any large backup files taking up space

find ${BACKUP_DIRECTORY} -type f -size +1G -exec ls -lh {} \;



# check for any other applications or processes consuming disk space

sudo lsof +L1 | awk '{print $1, $3, $4, $7}' | sort -h -k4


```

## Repair

### Identify and delete any unnecessary or unused data from the PostgreSQL database to free up disk space.
```shell


#!/bin/bash



# Set the parameters

PGHOST=${HOST}

PGUSER=${USERNAME}

PGDATABASE=${DATABASE_NAME}



# Identify and delete any unnecessary data from the database

psql -h $PGHOST -U $PGUSER -d $PGDATABASE -c "DELETE FROM ${TABLE_NAME} WHERE ${CONDITION};"


```

This incident type refers to a problem with a PostgreSQL database where it is reporting disk full errors. This means that the database has reached its full capacity and cannot store any more data. This can cause issues with the performance of the database and may result in data loss if not addressed promptly.


This incident type occurs when there are too many locks acquired on a Postgresql database instance. This can cause issues with database performance and functionality. It may be necessary to adjust the max\_locks\_per\_transaction setting in Postgresql to prevent this issue from occurring.


Postgresql too many locks acquired

This incident type refers to a situation where the Postgresql database has a high rollback rate, which means that a high percentage of transactions are being aborted compared to the committed ones. This can cause issues with data consistency and performance, and may require investigation and resolution by the responsible team. The incident details may include information about the affected database instance, the service or system impacted, the urgency level, and any related alerts or escalations.


Postgresql high rollback rate incident

This incident type refers to a scenario where there is a high rate of statement timeouts in a Postgresql database instance. This can lead to degraded performance and potentially impact the availability of the database. It is important to quickly identify and address the underlying cause of the timeouts to ensure the stability of the system.


Postgresql high rate statement timeout incident.

This incident type occurs when the maximum number of connections allowed to a Postgres database has been reached. This prevents new connections from being established and can result in errors or downtime. It is important to monitor connection usage and adjust the maximum connection limit as needed to prevent this issue from occurring.


Postgres Connection Limit Reached

This incident type occurs when the number of connections to a Postgres server is approaching its limit and may cause a saturation of the connection pool. This can lead to slow queries, timeouts, and other performance issues. It is important to monitor and manage the number of connections to ensure the smooth functioning of the database.


Postgres Connection Saturation

```shell
export PATH_TO_POSTGRESQL_DATA_DIRECTORY="PLACEHOLDER"

export DATABASE_NAME="PLACEHOLDER"

export TABLE_NAME="PLACEHOLDER"

export BACKUP_DIRECTORY="PLACEHOLDER"

export HOST="PLACEHOLDER"

export USERNAME="PLACEHOLDER"

export CONDITION="PLACEHOLDER"
```


### 1. Check the disk usage of the PostgreSQL data directory

```shell
df -h ${PATH_TO_POSTGRESQL_DATA_DIRECTORY}
```

### 2. Check the disk usage of the entire system to see if any other partitions are full

```shell
df -h
```

### 3. Check the size and usage of individual tables in the database

```shell
psql -d ${DATABASE_NAME} -c "SELECT pg_size_pretty(pg_total_relation_size('${TABLE_NAME}')) AS total_size;"
```

### 4. Check the size and usage of individual indexes in the database

```shell
psql -d ${DATABASE_NAME} -c "SELECT pg_size_pretty(pg_indexes_size('${TABLE_NAME}')) AS index_size;"
```

### 5. Check for any large and unnecessary files in the PostgreSQL data directory

```shell
find ${PATH_TO_POSTGRESQL_DATA_DIRECTORY} -type f -size +10M -exec ls -lh {} \;
```

### The disk where the PostgreSQL database is stored may have run out of storage space due to large database files or logs.

```shell
bash

#!/bin/bash



# check size of the PostgreSQL database files

du -hs ${PATH_TO_POSTGRESQL_DATA_DIRECTORY}



# check for any large backup files taking up space

find ${BACKUP_DIRECTORY} -type f -size +1G -exec ls -lh {} \;



# check for any other applications or processes consuming disk space

sudo lsof +L1 | awk '{print $1, $3, $4, $7}' | sort -h -k4


```


### Identify and delete any unnecessary or unused data from the PostgreSQL database to free up disk space.

```shell


#!/bin/bash



# Set the parameters

PGHOST=${HOST}

PGUSER=${USERNAME}

PGDATABASE=${DATABASE_NAME}



# Identify and delete any unnecessary data from the database

psql -h $PGHOST -U $PGUSER -d $PGDATABASE -c "DELETE FROM ${TABLE_NAME} WHERE ${CONDITION};"


```


PostgreSQL database reporting disk full errors.

Overview

Parameters

Debug

1. Check the disk usage of the PostgreSQL data directory

2. Check the disk usage of the entire system to see if any other partitions are full

3. Check the size and usage of individual tables in the database

4. Check the size and usage of individual indexes in the database

5. Check for any large and unnecessary files in the PostgreSQL data directory

The disk where the PostgreSQL database is stored may have run out of storage space due to large database files or logs.

Repair

Identify and delete any unnecessary or unused data from the PostgreSQL database to free up disk space.

Learn more

Related Runbooks

Postgresql too many locks acquired

Postgresql high rollback rate incident

Postgresql high rate statement timeout incident.

Postgres Connection Limit Reached

Support