| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | kasem adel <kasemadel8(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Wal file increase |
| Date: | 2025-12-15 12:14:38 |
| Message-ID: | b5cd7e01e64836a5f90eb49a15693f49a25595fe.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Raj | 2025-12-22 09:44:49 | OS upgrade vs Postgresql |
| Previous Message | kasem adel | 2025-12-15 08:19:40 | Re: Wal file increase |