Message-ID: <f277ace00b7a5213283708c53ca18f85e8adcc3c.camel@cybertec.at>
Subject: Re: Wal file increase
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: kasem adel <kasemadel8@gmail.com>, pgsql-admin
 <pgsql-admin@postgresql.org>
Date: Mon, 15 Dec 2025 07:31:05 +0100
In-Reply-To: 
 <CAP-pBm9kY6HafeGD-1vrL8UqaQLu2jFJthBjyOsypY=iGJRBxA@mail.gmail.com>
References: 
	<CAP-pBm9kY6HafeGD-1vrL8UqaQLu2jFJthBjyOsypY=iGJRBxA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.56.2 (3.56.2-2.fc42) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/f277ace00b7a5213283708c53ca18f85e8adcc3c.camel%40cybertec.at>
Precedence: bulk

On Sun, 2025-12-14 at 17:30 +0200, kasem adel wrote:
> Appreciate your usual support that we facing an issue when take pg_baseba=
ckup for 4 TB
> database in standby server and when backup finished we face huge number o=
f 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 slo=
t, WAL will
  pile up on the primary.  But what is the connection with pg_basebackup?

Yours,
Laurenz Albe