MIME-Version: 1.0
From: Vinay Oli <olivinay541@gmail.com>
Date: Fri, 13 Sep 2024 17:39:22 +0530
Message-ID: <CACHNdrD=sedje12LNvX6ZZkKYmHqW2DwoLvS4jHThc5MOv4+Rw@mail.gmail.com>
Subject: Reg: Size difference
To: pgsql-general@postgresql.org
Content-Type: multipart/alternative; boundary="000000000000a1bbd50621ff18cf"
Archived-At: <https://www.postgresql.org/message-id/CACHNdrD%3Dsedje12LNvX6ZZkKYmHqW2DwoLvS4jHThc5MOv4%2BRw%40mail.gmail.com>
Precedence: bulk

--000000000000a1bbd50621ff18cf
Content-Type: text/plain; charset="UTF-8"

Hi Team

I have been using PostgreSQL for the past 6 years. PostgreSQL has
significantly impacted my life, providing me with great opportunities for
knowledge and self-development.

I'm currently facing a strange issue with PostgreSQL 15.0. I have a
primary-standby setup that is in sync, with a replication slot in place.
There are 18 databases, and one of the databases on the primary side is 104
GB, while the same database on the standby side is 216 GB. Both are in sync
with zero delay.

Could this be a bug? If so, has it been resolved in newer releases? If it
is not a bug, how can this issue be fixed? Is there a solution or any
supporting documentation available?

WAL and log files are being rotated properly. The issue is with a database
named services_mfs. On the primary cluster, the services_mfs database is
104GB, but on the standby cluster, it is 216GB, even though both cluster
are in sync. The standby database is only used in case of a crash, which is
managed by a Patroni cluster with etcd.


Thanks,

Vinay Kumar

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

<div dir=3D"auto"><div style=3D"font-size:12.8px" dir=3D"auto"><div style=
=3D"width:361.091px;margin:16px 0px"><div><div dir=3D"auto"><p>Hi Team</p><=
p></p><p>I have been using PostgreSQL for the past 6 years. PostgreSQL has =
significantly impacted my life, providing me with great opportunities for k=
nowledge and self-development.</p><p></p><p>I&#39;m currently facing a stra=
nge issue with PostgreSQL 15.0. I have a primary-standby setup that is in s=
ync, with a replication slot in place. There are 18 databases, and one of t=
he databases on the primary side is 104 GB, while the same database on the =
standby side is 216 GB. Both are in sync with zero delay.</p><p></p><p>Coul=
d this be a bug? If so, has it been resolved in newer releases? If it is no=
t a bug, how can this issue be fixed? Is there a solution or any supporting=
 documentation available?</p><p>WAL and log files are being rotated properl=
y. The issue is with a database named services_mfs. On the primary cluster,=
 the services_mfs database is 104GB, but on the standby cluster, it is 216G=
B, even though both cluster are in sync. The standby database is only used =
in case of a crash, which is managed by a Patroni cluster with etcd.</p><p>=
<br></p><p><br></p><p>Thanks,</p><p>Vinay Kumar</p></div></div></div><div s=
tyle=3D"height:0px"></div></div><br></div>

--000000000000a1bbd50621ff18cf--