Re: db maintanance problem VACUUM FULL

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: db maintanance problem VACUUM FULL
Date: 2025-06-12 13:29:48
Message-ID: CANzqJaBUw_N9+rtdb88Fbhdw4T8m=1_52Xfwa988+0bP4retJQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Jun 12, 2025 at 9:24 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
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.
>

The dreaded Software Compatibility Matrix often restricts how big of a jump
is possible when upgrading databases (and even Python).

Multi-phase upgrades spanning months are quite common.

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Rachel Roch 2025-06-13 18:08:11 pg_restore ERROR: permission denied to change default privileges
Previous Message Ron Johnson 2025-06-12 13:26:34 Re: db maintanance problem VACUUM FULL