Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uPi0K-00E8I5-OQ for pgsql-general@arkaria.postgresql.org; Thu, 12 Jun 2025 13:30:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uPi0I-00ConD-SZ for pgsql-general@arkaria.postgresql.org; Thu, 12 Jun 2025 13:30:03 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uPi0I-00Con2-Ca for pgsql-general@lists.postgresql.org; Thu, 12 Jun 2025 13:30:03 +0000 Received: from mail-oa1-x36.google.com ([2001:4860:4864:20::36]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uPi0H-001bvM-1D for pgsql-general@lists.postgresql.org; Thu, 12 Jun 2025 13:30:02 +0000 Received: by mail-oa1-x36.google.com with SMTP id 586e51a60fabf-2da73158006so668665fac.0 for ; Thu, 12 Jun 2025 06:30:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1749735000; x=1750339800; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=rlhW/v7ixaO+wKyJnMR/s5sNzyTvoY07J8lFqpfhnOI=; b=nT+WIRD3nKVvqHplVbSixXdZhP0/PQtcxLH4wH8OLdh84s1QURZUDjPCjxtO+r6Okn Mm1Q+JPGzeJi/pd6zezj9VVlh4gBkxB74MhrzR+2IZy4AnrAKopZAfNpVAemAHzJGVM7 p2H3k9DVVL8xVU2sOh5OHJz25dgqzXdiPH27RA9A+X4Xn2IiZj/vJ+5Fbi7iiJEWydUz PSOyUSbJCPaKRC8okAXa1a9X3d27YhiWSsRIw0X30UMJGVbb+cjc6hhJDCE6ABZtRJCG l0LvzPrKzFKjyrEApUk5cg/9G11DRTqTdi+HuKnXW61TVsftIDuiZYjny8598N+fmMZ7 F/ww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749735000; x=1750339800; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=rlhW/v7ixaO+wKyJnMR/s5sNzyTvoY07J8lFqpfhnOI=; b=VMjjztHaK7lOmDDSm2GAfF5c6cWQo6TeY5JPxdtSqs5j/nXSQ6IoJZmxIr6FL4+umJ BQ5f7O7uGHuO0XFuf76Xbzyh5qBXrLgxMqSQ5A0YVlcPFVKrKEm4lsJnyeyBkL/f3qH8 HT6IB3JccGGfJS7sdWJghs7Z+tEDqXFKD0xE7eXD2Wdy5nVn/URrsBkj11k0PvahU+uQ 4NOIDt3TIMf/UpdUCUJaAV/EGHOhBdRHI57yGCioFaJkmDNDzqtU2oIqcDquUlKrqgBL lSxXkk2qd4uJwecCngVp23SciHwINWUFfAmRi2j5as0CsGZV4svZ0zzD5oIZ3GH4sUrH oZ1Q== X-Gm-Message-State: AOJu0YwQJ5FZJvLVHcKirHocFNS2aXg7M0CRWMoKmYQRPHJTKtBjgQER SajU+sVVZ3WuRXmhwNSQ6sIPWEW5CVWDHv3OsvlBiIUSWV5nXX87HnScwH6uws6ROqq0fwCD1Y2 C704Ll+vEbCNVphvDuu8Et8iB1t0m4Y9Pcw== X-Gm-Gg: ASbGncv702fd9pN4IHaK1BfVht+/TvA8lZ3gPLXEr4BUW0GnLd/9g8uEi6HJ57DBPeb YaPZtsMPd2bgC6jED0+x5wzF9jW45dmonnIAPF6Ip9aIK4FPlhLWLpTazKLcgvkziluOgjMOZlU vDWZ3TNsW/frB7ZQ2VGMjFbrYjw4SMn5J/I7Try4h4aQ/J X-Google-Smtp-Source: AGHT+IGBqAxN6PGpBK9D0yYEhFHDW/3nNxbA5E+0xgUbtUvQ61pFJa451O7OmeQpJClahwBJ9L9yfrNCDv6kScyU7xM= X-Received: by 2002:a05:6870:fe82:b0:2d5:ba2d:80e4 with SMTP id 586e51a60fabf-2eab70f75demr1485977fac.24.1749735000278; Thu, 12 Jun 2025 06:30:00 -0700 (PDT) MIME-Version: 1.0 References: <61b05ae722c2b21cd63d98544c55ecc0e35aa887.camel@cybertec.at> In-Reply-To: <61b05ae722c2b21cd63d98544c55ecc0e35aa887.camel@cybertec.at> From: Ron Johnson Date: Thu, 12 Jun 2025 09:29:48 -0400 X-Gm-Features: AX0GCFsrTztl2tktL_d4aBdzwVzV_PCMaLg5tnV8y87uAbcTonXh99P-Xfdr0ys Message-ID: Subject: Re: db maintanance problem VACUUM FULL To: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000248b7c06375fedd3" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000248b7c06375fedd3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Jun 12, 2025 at 9:24=E2=80=AFAM 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 th= e > 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. --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000248b7c06375fedd3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Jun 12, 2025 at 9:24=E2=80=AFAM L= aurenz Albe <laurenz.albe@cy= bertec.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 t= he 9.6.24 version.
> We didn't want to make a big jump.

But you should have.=C2=A0 v12 is out of support.

=
The dreaded Software Compatibility Matrix often restricts how bi= g of a jump is possible when upgrading databases (and even Python).
=C2=A0
Multi-phase upgrades spanning months are quite common.<= /div>

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