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 1seHMz-005fEI-VJ for pgsql-admin@arkaria.postgresql.org; Wed, 14 Aug 2024 17:01:09 +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 1seHMx-00BbQE-Cr for pgsql-admin@arkaria.postgresql.org; Wed, 14 Aug 2024 17:01:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1seHMx-00BbQ6-1E for pgsql-admin@lists.postgresql.org; Wed, 14 Aug 2024 17:01:07 +0000 Received: from mail-ua1-x935.google.com ([2607:f8b0:4864:20::935]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1seHMq-004qT3-JE for pgsql-admin@lists.postgresql.org; Wed, 14 Aug 2024 17:01:06 +0000 Received: by mail-ua1-x935.google.com with SMTP id a1e0cc1a2514c-842f91f2545so12246241.3 for ; Wed, 14 Aug 2024 10:01:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1723654859; x=1724259659; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=eWyC29kGs5Jn9W+uBksmOOB2pkAVI44PSXKulDCSmvQ=; b=Qb/IixkEpoeZxajZy3zR3pTnEDAZ/SUWbGdpHpyBiCZ20v47/YsbYhZwVCx1neA7r4 w9vHSeD9gWGSD/4faGuGRkZlOLipRMrJoQte+Sd9MSOMBgXXRoNeL4vDmrZnkwNqgm1c hfIsMVzCJSkInt1/3kNGO7IYSYt0PGKcYjoptUnWZALGiN2KFcPNNJNnU4wHAgENSxSE mPLXUQ2WyRf7uSb31oBhE3NRAUiX7AUntnZHRkRxY1UW8rVpIyJW/gvqUTj3HwfLkvuK nQl/LKqqVPVZNUrMDkH93aMLv3ewHFm1rqb8PngOyD8NBwrXqmTYqXtebby7J41JS9Yp iOlg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723654859; x=1724259659; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=eWyC29kGs5Jn9W+uBksmOOB2pkAVI44PSXKulDCSmvQ=; b=EbYniCZj1eEtsHbCfW+sLwbzg5AD8EeY1ldml7xix07uFr2f8H01RjMpZBaBxqAkWr N1rkv2Jv6Z0RGziawFmgPUpq6IsDdJsWyFo7cK84enbLlK+sKYj8F8E/Q4Nu1Rn35Fdy rz0j+4ZjVL8yZuytdEIonhjOct7mXHQgLVX4FcvSACo636M4eOsCnmsVoBrgr6c5A1nD vYmQdQhzkEV4RUiR45ekEe9eHn0X6u658/TTfx+Ey7v6Nu7tCn/UuWgADuveRQKCGXi/ f9E83vv6YXlQQbW7/WyKzT3yY1FtzQ8R1N96j6jFXX6KxYogXQCXDrRxmcfgl9lP91b2 L7uA== X-Gm-Message-State: AOJu0YxjCdCEJcvjUBnxVwgThQBB3Jv+/wWPFDbG/OzW80T2mwFcrD7b eaP7zOYUrkl8irKgPsRIZmJl54iJ8flfqHhAZtL1cdoYJmglPnRQL7xENj6NwHpLztCfjrAS+5a UfFFO0lG/IBVoNlwxq4EJVz4pxYl101A4 X-Google-Smtp-Source: AGHT+IEytPiNrz8+oNIXL+R0LzTCrqUAGuOFcfnRasUL/OQi0B9PG+2Zw5BfjREozqse13mphczWYZqVTkyBGHVU4HY= X-Received: by 2002:a05:6122:2008:b0:4f2:e9eb:951e with SMTP id 71dfb90a1353d-4fad21f5fe3mr4340023e0c.10.1723654858359; Wed, 14 Aug 2024 10:00:58 -0700 (PDT) MIME-Version: 1.0 From: tiamoh m Date: Wed, 14 Aug 2024 13:00:46 -0400 Message-ID: Subject: LIsten Errror To: pgsql-admin@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000008c4c42061fa7ab24" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000008c4c42061fa7ab24 Content-Type: text/plain; charset="UTF-8" Hello all, We keep having these errors below in our different clusters. LISTEN| PGE-58P01: ERROR: could not access status of transaction 4543382428 When it starts occurring, so far the only way to stop it has been to restart. Is there any permanent fix for this issue? Thank you Tiamoh J --0000000000008c4c42061fa7ab24 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello all,


We keep havin= g these errors=C2=A0 below in our different clusters.

<= div>LISTEN| PGE-58P01: ERROR:=C2=A0 could not access status of transaction = 4543382428

When it starts=C2=A0occurring, so f= ar the only way to stop it has been to restart.=C2=A0=C2=A0

<= /div>
Is there any permanent=C2=A0fix for this=C2=A0issue?

Thank you
Tiamoh=C2=A0J
--0000000000008c4c42061fa7ab24--