| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | kasem adel <kasemadel8(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Wal file increase |
| Date: | 2025-12-15 06:31:05 |
| Message-ID: | f277ace00b7a5213283708c53ca18f85e8adcc3c.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Sun, 2025-12-14 at 17:30 +0200, kasem adel wrote:
> Appreciate your usual support that we facing an issue when take pg_basebackup for 4 TB
> database in standby server and when backup finished we face huge number of wal file
> with huge size generated for 6 hours the cause replication interruption.
If you want help with that, you will have to give us enough information to explain what
happened.
- What exactly is a "replication interruption", and how do you diagnose it?
- Are you using streaming replication or logical replication?
- If it is streaming replication, are you using a replication slot?
- It is expected that if you suspend replication and have a replication slot, WAL will
pile up on the primary. But what is the connection with pg_basebackup?
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | kasem adel | 2025-12-15 07:25:58 | Re: Wal file increase |
| Previous Message | kasem adel | 2025-12-14 15:30:03 | Wal file increase |