public inbox for [email protected]
help / color / mirror / Atom feedFrom: Laurenz Albe <[email protected]>
To: kasem adel <[email protected]>
To: pgsql-admin <[email protected]>
Subject: Re: Wal file increase
Date: Mon, 15 Dec 2025 13:14:38 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <AM4P193MB29416485C01CC7DCC529C592AEADA@AM4P193MB2941.EURP193.PROD.OUTLOOK.COM>
References: <CAP-pBm9kY6HafeGD-1vrL8UqaQLu2jFJthBjyOsypY=iGJRBxA@mail.gmail.com>
<[email protected]>
<AM4P193MB2941220558624561A6A5F6EBAEADA@AM4P193MB2941.EURP193.PROD.OUTLOOK.COM>
<[email protected]>
<AM4P193MB29416485C01CC7DCC529C592AEADA@AM4P193MB2941.EURP193.PROD.OUTLOOK.COM>
On Mon, 2025-12-15 at 08:19 +0000, kasem adel wrote:
> > -What exactly is a "replication interruption", and how do you diagnose it?
> We see replication slot restart every time in these period
I have never heard of a "replication slot restart"...
> > - 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.
You probably need to hire an expert to have a look at your system and find
out what *really* is going on there.
Yours,
Laurenz Albe
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Wal file increase
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox