Re: db maintanance problem VACUUM FULL

On Thu, Jun 12, 2025 at 9:24 AM Laurenz Albe wrote: > On Thu, 2025-06-12 at 15:14 +0200, Pavol Sekeres wrote: > > 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. > > But you should have. v12 is out of support. > T

Re: db maintanance problem VACUUM FULL

On Thu, Jun 12, 2025 at 9:14 AM Pavol Sekeres wrote: > Hi, > > We recently updated our production database to PostgreSQL 12.22 from the > 9.6.24 version. > Will you soon make another jump to a supported version? > We didn't want to make a big jump. > It is around 2 TB in size with one stand-by

Re: db maintanance problem VACUUM FULL

On Thu, 2025-06-12 at 15:14 +0200, Pavol Sekeres wrote: > 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. But you should have. v12 is out of support. > It is around 2 TB in size with one stand-by replica of equal si

db maintanance problem VACUUM FULL

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 h