Re: Wal file increase - Mailing list pgsql-admin

From kasem adel
Subject Re: Wal file increase
Date
Msg-id AM4P193MB2941220558624561A6A5F6EBAEADA@AM4P193MB2941.EURP193.PROD.OUTLOOK.COM
Whole thread Raw
In response to Re: Wal file increase  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: Wal file increase
List pgsql-admin
Thanks for your support We have physical replication connection with Postgres node standby and have another replication slot with logical replication with another node and every day after run pg_basebackup we face huge number of file created and size per every hour is 23GB and in normal size is 0.8 GB and in logical replication we see in logs it’s in same checkpoint but baseline change and we run pg_basebackup with -X fetch -C fast.
Thanks

من: Laurenz Albe <laurenz.albe@cybertec.at>
‏‏تم الإرسال: Monday, December 15, 2025 8:31:05 AM
إلى: kasem adel <kasemadel8@gmail.com>; pgsql-admin <pgsql-admin@postgresql.org>
‏‏الموضوع: Re: Wal file increase
 
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

pgsql-admin by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Wal file increase
Next
From: Laurenz Albe
Date:
Subject: Re: Wal file increase