Message-ID: <d58f28bf89b8606a9b15e9a957a1a26f00e7c2e7.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 09:09:00 +0100
In-Reply-To: 
 <AM4P193MB2941220558624561A6A5F6EBAEADA@AM4P193MB2941.EURP193.PROD.OUTLOOK.COM>
References: 
	<CAP-pBm9kY6HafeGD-1vrL8UqaQLu2jFJthBjyOsypY=iGJRBxA@mail.gmail.com>
	 <f277ace00b7a5213283708c53ca18f85e8adcc3c.camel@cybertec.at>
	 <AM4P193MB2941220558624561A6A5F6EBAEADA@AM4P193MB2941.EURP193.PROD.OUTLOOK.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/d58f28bf89b8606a9b15e9a957a1a26f00e7c2e7.camel%40cybertec.at>
Precedence: bulk

On Mon, 2025-12-15 at 07:25 +0000, kasem adel wrote:
> Thanks for your support We have physical replication connection with Post=
gres node standby
> and have another replication slot with logical replication with another n=
ode 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=
=E2=80=99s in same
> checkpoint but baseline change and we run pg_basebackup with -X fetch -C =
fast.

pg_basebackup does not increase the WAL volume, except by the full-page ima=
ges that get
written after any checkpoint.  So you'd need to find an explanation for tha=
t.

"-X fetch" is not a good choice.  Use "-X stream".

Anyway, you didn't answer all my questions.

Yours,
Laurenz Albe