Thread: Reg: Size difference

Reg: Size difference

From
Vinay Oli
Date:

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?




Thanks & Regards,

Vinay Kumar

Re: Reg: Size difference

From
Aleksander Alekseev
Date:
Hi,

> 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?
Isthere a solution or any supporting documentation available?
 

Hard to tell based on the provided information. Do you know which
files differ in particular? It could be as simple as a huge text log
file that was never rotated.

Also I'm a bit surprised that you use 15.0. I know several people who
believe that using the next major version of Postgres before the .2
minor release is not the best idea, and I can understand this point of
view. Postgres 15 had 8 updates in the past several years [1] with
multiple improvements / bug fixes in every one of them. You should
probably consider installing these updates.

[1]: https://www.postgresql.org/docs/release/15.8/

-- 
Best regards,
Aleksander Alekseev



Re: Reg: Size difference

From
Vinay Oli
Date:

Hi,


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


On Fri, 13 Sept 2024 at 16:08, Aleksander Alekseev <aleksander@timescale.com> wrote:
Hi,

> 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?

Hard to tell based on the provided information. Do you know which
files differ in particular? It could be as simple as a huge text log
file that was never rotated.

Also I'm a bit surprised that you use 15.0. I know several people who
believe that using the next major version of Postgres before the .2
minor release is not the best idea, and I can understand this point of
view. Postgres 15 had 8 updates in the past several years [1] with
multiple improvements / bug fixes in every one of them. You should
probably consider installing these updates.

[1]: https://www.postgresql.org/docs/release/15.8/

--
Best regards,
Aleksander Alekseev