pg_wal directory on the secondary server is getting full, retaining WAL files from the past four months. However, on the primary server its fine, the pg_wal size is only 1.5GB, whereas the secondary has grown to 28GB.
I confirmed that the configuration parameters are identical on both servers, so Im unsure why this is happening only on the secondary.
Could you suggest anything on that?
Do you have a backup running against the secondary?
Than that backup might have caused the WAL backlog. Which software is it?
It's taking by crontab
That's only executing the backup tool. Question is still which backup tool?
Pg_basebackup and pg_dump
Then it's probably a WAL lag of pg_basebackup. You need to take care of finishing the following of backups yourself, it is not managed. Think about using https://pgbackrest.org/, it will take of cleaning up itself as it stops following WAL automatically as configured.
Обсуждают сегодня