MIME-Version: 1.0
From: Vinay Oli <olivinay541@gmail.com>
Date: Sat, 14 Sep 2024 22:49:07 +0530
Message-ID: <CACHNdrBT4MTTo_EGSHke+QxXwUUV40miraQwk4GR1wzsiogwnw@mail.gmail.com>
Subject: Reg: Size difference
To: pgsql-general@postgresql.org
Content-Type: multipart/alternative; boundary="0000000000003334a50622178a23"
Archived-At: <https://www.postgresql.org/message-id/CACHNdrBT4MTTo_EGSHke%2BQxXwUUV40miraQwk4GR1wzsiogwnw%40mail.gmail.com>
Precedence: bulk

--0000000000003334a50622178a23
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

--0000000000003334a50622178a23
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"><div dir=3D"aut=
o"><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. Po=
stgreSQL has significantly impacted my life, providing me with great opport=
unities for knowledge and self-development.</p><p></p><p>I&#39;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 dat=
abase on the standby side is 216 GB. Both are in sync with zero delay.</p><=
p></p><p>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 a=
ny supporting documentation available?</p><p>WAL and log files are being ro=
tated properly. The issue is with a database named services_mfs. On the pri=
mary cluster, the services_mfs database is 104GB, but on the standby cluste=
r, 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.</p><p><br></p><p><br></p><p>Thanks,</p><p>Vinay Kumar</p></div></div=
></div><div style=3D"height:0px"></div></div><br></div></div></div><div sty=
le=3D"height:0px"></div></div><br></div>

--0000000000003334a50622178a23--