db maintanance problem VACUUM FULL - Mailing list pgsql-general

From Pavol Sekeres
Subject db maintanance problem VACUUM FULL
Date
Msg-id CA+RPunpqzys-rqsH9Xia8KWJ2+mR=V_TXe4Ca+JDV7bvmym8TQ@mail.gmail.com
Whole thread
Responses Re: db maintanance problem VACUUM FULL
Re: db maintanance problem VACUUM FULL
List pgsql-general
Hi,

We recently updated our production database to PostgreSQL 12.22 from the 9.6.24 version.
We didn't want to make a big jump.
It is around 2 TB in size with one stand-by replica of equal size.
The database is more than 5 years old.

We do run AUTOVACUUM processes on all tables periodically.
We have never run VACUUM FULL on any table.
This is because we can't afford to lock out tables for a long time.

Tables can be more than 100GB in size.
They are being updated daily.
Also due to GDPR old data is erased on a daily basis.
We think these tables might get eventually bloated.

Can this be a problem?

If yes, is there any other solution outside locking the database?
Should we try to solve this problem by creating a logical replica of the database?
We would then promote the replica to primary.
After that, we would drop the old database.
Is this possible without a big downtime?
Is this even a good idea?

Our database uses a wal_level 'replica'.
As I understand it, this setting would first have to be switched to 'logical'.

Thank you for your answer,
Best regards,
Pavol Sekeres

pgsql-general by date:

Previous
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: Logical Replication Memory Allocation Error - "invalid memory alloc request size"
Next
From: Laurenz Albe
Date:
Subject: Re: db maintanance problem VACUUM FULL