MIME-Version: 1.0
From: Devvrat Mittal <devvrat@tecorelabs.com>
Date: Mon, 28 Apr 2025 12:48:15 +0530
Message-ID: <CAN8+pfqikxnMgocorGbgsP08N4s6XJ8LJAT3advK6urZ29Xj2A@mail.gmail.com>
Subject: Wal Files not removing automatically
To: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000006f1d120633d17da8"
Archived-At: <https://www.postgresql.org/message-id/CAN8%2BpfqikxnMgocorGbgsP08N4s6XJ8LJAT3advK6urZ29Xj2A%40mail.gmail.com>
Precedence: bulk

--0000000000006f1d120633d17da8
Content-Type: text/plain; charset="UTF-8"

Hello,

I have 3 nodes on which i have configured repmgr on 1st node primary, on
2nd standby and on 3rd witness. I have also configured pgbackrest on the
primary and witness node.
I'm using fivetran as a replication slot. i have also set the parameters
which are:
wal_level = 'logical'
synchronous_commit = local
wal_log_hints = 'on'
archive_mode = on
max_wal_senders = 10
wal_keep_segments = 32
max_replication_slots = 10
hot_standby = on
wal_sender_timeout = 300s
wal_receiver_timeout = 300s
max_connections = 1000
shared_buffers = 15GB
effective_cache_size = 45GB
maintenance_work_mem = 2GB
checkpoint_completion_target = 0.9
wal_buffers = 16MB
default_statistics_target = 100
random_page_cost = 1.1
effective_io_concurrency = 200
work_mem = 3932kB
min_wal_size = 2GB
max_wal_size = 8GB

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?

--0000000000006f1d120633d17da8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello, <br><br>I have 3 nodes on which i have configured r=
epmgr on 1st node primary, on 2nd standby and on 3rd witness. I have also c=
onfigured pgbackrest on the primary and witness node.<br>I&#39;m using five=
tran as a replication slot. i have also set the parameters which are:<br>wa=
l_level =3D &#39;logical&#39;<br>synchronous_commit =3D local<br>wal_log_hi=
nts =3D &#39;on&#39;<br>archive_mode =3D on<br>max_wal_senders =3D 10<br>wa=
l_keep_segments =3D 32<br>max_replication_slots =3D 10<br>hot_standby =3D o=
n<br>wal_sender_timeout =3D 300s<br>wal_receiver_timeout =3D 300s<br>max_co=
nnections =3D 1000<br>shared_buffers =3D 15GB<br>effective_cache_size =3D 4=
5GB<br>maintenance_work_mem =3D 2GB<br>checkpoint_completion_target =3D 0.9=
<br>wal_buffers =3D 16MB<br>default_statistics_target =3D 100<br>random_pag=
e_cost =3D 1.1<br>effective_io_concurrency =3D 200<br>work_mem =3D 3932kB<b=
r>min_wal_size =3D 2GB<br>max_wal_size =3D 8GB<br><br>And these parameters =
also set on the other sites too. Now the issue is the wal files are removin=
g automatically. And the restart_lsn is also not changing automatically. Bu=
t when i drop the replication slot and recreate it. After i create the repl=
ication slot the restart_lsn change but after that i face the same issue th=
at restart_lsn is not changing. So i wanna know is it kind of bug or it&#39=
;s a issue from from database side? <br>=C2=A0</div>

--0000000000006f1d120633d17da8--