From 05b2657065279cfc357b2e77866d444ed3722013 Mon Sep 17 00:00:00 2001 From: RahulSrivastav14 Date: Tue, 20 May 2025 13:22:29 +0530 Subject: [PATCH] Update > Database Upgrade > storage exhaustion caution message --- .../disaster-recovery/database-upgrade/index.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/guides/hosting-guardrails/disaster-recovery/database-upgrade/index.md b/docs/guides/hosting-guardrails/disaster-recovery/database-upgrade/index.md index 80c87453..5b0b09fa 100644 --- a/docs/guides/hosting-guardrails/disaster-recovery/database-upgrade/index.md +++ b/docs/guides/hosting-guardrails/disaster-recovery/database-upgrade/index.md @@ -259,6 +259,9 @@ In a new session, initiate the `pg_dump` process using the `snapshot ID` obtaine ```shell nohup time pg_dump -h $SOURCE -U master --snapshot="00000062-000182C4-1" -F c -b -v -f data.dump turbot > dump.log 2>&1 & ``` + + > [!CAUTION] + > Enabling logical replication before a long pg_dump/restore can lead to WAL buildup and storage exhaustion. It is recommended to enable RDS storage autoscaling to prevent out-of-space errors during migration. ### Monitor Check the `dump.log` file to confirm the process has begun. Look for log entries indicating `table contents are being dumped`.