Re: Wal Files not removing automatically - Mailing list pgsql-general

From Tom Lane
Subject Re: Wal Files not removing automatically
Date
Msg-id 699028.1745838535@sss.pgh.pa.us
Whole thread Raw
In response to Wal Files not removing automatically  (Devvrat Mittal <devvrat@tecorelabs.com>)
List pgsql-general
Devvrat Mittal <devvrat@tecorelabs.com> writes:
> And these parameters also set on the other sites too. Now the issue is the
> wal files are removing automatically. And the restart_lsn is also not
> changing automatically. But when i drop the replication slot and recreate
> it. After i create the replication slot the restart_lsn change but after
> that i face the same issue that restart_lsn is not changing. So i wanna
> know is it kind of bug or it's a issue from from database side?

The entire point of a replication slot is that it prevents WAL from
being discarded until whatever is supposed to read from the slot
has consumed that WAL.  So apparently nothing is reading from that
slot, which means there is something wrong with the way
you've connected up your replication setup.  I would have thought
you'd be using slots to feed your standby and witness servers
(and I don't understand why you don't have two slots, one for each).

            regards, tom lane



pgsql-general by date:

Previous
From: Marc Millas
Date:
Subject: Re: shared buffers
Next
From: Tim Starling
Date:
Subject: Re: Upsert error "column reference is ambiguous"