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 1sDPAh-00CW0d-7j for pgsql-general@arkaria.postgresql.org; Sat, 01 Jun 2024 13:53:24 +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 1sDPAe-002yEE-V0 for pgsql-general@arkaria.postgresql.org; Sat, 01 Jun 2024 13:53:20 +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 1sDPAe-002yBn-H5 for pgsql-general@lists.postgresql.org; Sat, 01 Jun 2024 13:53:20 +0000 Received: from mail-oa1-x35.google.com ([2001:4860:4864:20::35]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sDPAc-002yO0-4e for pgsql-general@postgresql.org; Sat, 01 Jun 2024 13:53:19 +0000 Received: by mail-oa1-x35.google.com with SMTP id 586e51a60fabf-24c9f628e71so1506261fac.1 for ; Sat, 01 Jun 2024 06:53:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717249997; x=1717854797; darn=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=C57iAnx6mNEAinmKCNKDFGtiYxJgowETKmsuX93Zmr4=; b=XDhOKgs9jjGpZebo8vv7n5sEuBu+XTlI4NfUCENqesIRw2fJEFq8l+j7gpMqzCMIDQ xF+1/lWMEEHuvOD5Bk2cwR4Gat1LetmTeUs9lD7tP986f80Z6DTYYWlbnRGfaXMtQ50X e1F1fzNpdq5E6LWwJ50VHZn72BQDcoMRFQG02M4oe2mGvt40z+EGnhy5yXD52MYhSfYK cVq9KwDCcuxLhYb1KUoErmj8aB+tgcEVuU8AjawCixARQ7wAjTTwqecvg5Gb2me23pcx 0Ea0TH90/a/q4ugeWjWM0FybeNoAtYAvQwZ6d3cHSHxbMwV6Fxpac8e0obsgvOX8jPMK 66Ww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717249997; x=1717854797; 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=C57iAnx6mNEAinmKCNKDFGtiYxJgowETKmsuX93Zmr4=; b=qeGkixwwKWgA0NtvsnTMpKYx0UDf+74jCm/ZCSRsn2xf5Sxbz7HWK66boxtZTKDNIV ZrNUsdJ2eaS/JkiPGHx9rygVnD7oX+vSaABqRNpFRGkBdpr1vbIdjguucqY/ZBqF4Vzy MKLF86rVkPR/JW3ViIzmChO9nzyX8ZAtsdDW3h7RSQqam8Q+Nbjol6qxsBiXRz6UZm7c KNPi4j+1vwSPNlKjxHKsRPpLgpYAWBljmhIAI7pOLvqNM8X7ypawTABv0u3yoICjuFBW W7CjbybZaQXF7g9HycPdRq0UJ5hIL5693EOCspEneSrCC8d3fnBtN9VVFb8f1WlNV0g6 O0hQ== X-Gm-Message-State: AOJu0Yxhjs3stIuDObliPibYAivxqmI7ww/AGbsVcQit+PhLLWnYRYn3 h4kYveFZazX+WoOG3kdlMQtPeRQK5dfu3JTwTyGi2iCdk9wjHslvz3LpvOrz/BKZ0Eq+H2iGayv 0VEpBoFzWiCsfbcMELbArA6YX9sD07rMw X-Google-Smtp-Source: AGHT+IGypf+bm/AhXkiKp9dgp26RV1mivaywfo+KbypUdQUDWjbQ1UZT37pLgSyxQhcRT5ZdGiGEd2v8u1uwne+WpNg= X-Received: by 2002:a05:6870:724a:b0:250:8255:e793 with SMTP id 586e51a60fabf-2508b993d50mr5489420fac.23.1717249996701; Sat, 01 Jun 2024 06:53:16 -0700 (PDT) MIME-Version: 1.0 References: <4fbdd9760b329bccbdd62b6645d5977bee957e0d.camel@cybertec.at> In-Reply-To: From: Ron Johnson Date: Sat, 1 Jun 2024 09:53:05 -0400 Message-ID: Subject: Re: ERROR: found xmin from before relfrozenxid; MultiXactid does no longer exist -- apparent wraparound To: pgsql-general Content-Type: multipart/alternative; boundary="0000000000000b487a0619d46cd0" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000000b487a0619d46cd0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, May 31, 2024 at 1:25=E2=80=AFPM Alanoly Andrews wrote: > Yes, and I know that upgrading the Postgres version is the stock answer > for situations like this. The upgrade is in the works. > *Patching *was the solution. It takes *five minutes*. Here's how I did it (since our RHEL systems are blocked from the Internet, and I had to manually d/l the relevant RPMs): $ sudo -iu postgres pg_ctl stop -wt9999 -mfast $ sudo yum install PG96.24_RHEL6/*rpm $ sudo -iu postgres pg_ctl start -wt9999 You'll have a bit of effort finding the PG10 repository, since it's EOL, but it can be found. --0000000000000b487a0619d46cd0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, May 31, 2024 at 1:25=E2=80=AFPM A= lanoly Andrews <alanolya@invera.c= om> wrote:
Yes, and I know that upgrading the Postgres version is the st= ock answer for situations=C2=A0like this. The upgrade is in the works.

Patching=C2=A0w= as the solution.=C2=A0 It takes five minutes.
Here's h= ow I did it (since our RHEL systems are blocked from the Internet, and I ha= d to manually d/l the relevant RPMs):
$ sudo -iu postgres pg_ctl = stop -wt9999 -mfast
$ sudo yum install PG96.24_RHEL6/*rpm
$ sudo -iu postgres pg_ctl start -wt9999

Yo= u'll have a bit of=C2=A0effort finding=C2=A0the PG10 repository, since = it's EOL, but it can be found.

--0000000000000b487a0619d46cd0--