Re: Wal file increase

Dear @Laurenz Albe<mailto:laurenz(dot)albe(at)cybertec(dot)at>,

-What exactly is a "replication interruption", and how do you diagnose it?
We see replication slot restart every time in these period
- Are you using streaming replication or logical replication?
I have streaming replication for one node and another logical replication
- If it is streaming replication, are you using a replication slot?
Yes have 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?
Yes still exist.
احصل على Outlook لـ iOS<https://aka.ms/o0ukef>
________________________________
من: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
‏‏تم الإرسال: Monday, December 15, 2025 10:09:00 AM
إلى: kasem adel <kasemadel8(at)gmail(dot)com>; pgsql-admin <pgsql-admin(at)postgresql(dot)org>
‏‏الموضوع: Re: Wal file increase

On Mon, 2025-12-15 at 07:25 +0000, kasem adel wrote:
> 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.

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

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

Anyway, you didn't answer all my questions.

Yours,
Laurenz Albe