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 1sD63E-00A7oP-5V for pgsql-general@arkaria.postgresql.org; Fri, 31 May 2024 17:28:25 +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 1sD63D-00Dapb-T1 for pgsql-general@arkaria.postgresql.org; Fri, 31 May 2024 17:28:23 +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 1sD3KY-00CND5-Aq for pgsql-general@lists.postgresql.org; Fri, 31 May 2024 14:34:06 +0000 Received: from mail1.bemta35.messagelabs.com ([67.219.250.112]) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sD3KT-002pYP-8e for pgsql-general@lists.postgresql.org; Fri, 31 May 2024 14:34:05 +0000 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrAJsWRWlGSWpSXmKPExsWSoe/9Qvfa/cg 0g1er2CzOzDvEbPF02ns2ByaPJ1emM3kcbSoMYIpizcxLyq9IYM140C5ZcDunYtbvduYGxr64 LkYuDkaBpcwSn3u3MkI4i1glpr59yQ7hbGCU6J+9BcxhEdjGIjH79UkWEEdIYD6TxPpVV9ggn IeMEp/ObWTqYuTkYBPQlpg9aycLiC0iIC/xd/cRsDizgK/Eg4edzF2MHBzCAoUSvVeLQEwRgS KJX00qEKaTxL01xSDFLAKqEmeO7mcGsXkF4iV6Zm1jhtj0mFFixaUdYNM5BYIk2jZPAJvOKCA rsfvsdahN4hL75u8Ga5YQEJBYsuc8lC0q8fLxP1aIoTwScxZ3M4LsZRQokTj3kgOiRFbi0nyQ MIjtILGp8x07hO0r8bt5GROELSexqvchC4QtLzFt0XuoGj+J/jefwGElIdDNL/F2WR8bhHOPU eJ7TyMbRJWBxLxvR6ASxwQlDva1sE5g1JmF5HAIO09iZe9vxllgxwpKnJz5hAUibiDx/tx8qB ptiWULX0PZ+hIbv5xlRBZfwMi+itGsOLWoLLVI19BQL6koMz2jJDcxM0cvsUo3Ua+0WLc8tbh E10gvsbxYL7W4WK+4Mjc5J0UvL7VkEyMwaaUUJZrtYLy9vkn/EKMkB5OSKK/f1Mg0Ib6k/JTK jMTijPii0pzU4kOMMhwcShK8mneBcoJFqempFWmZOcAECpOW4OBREuEVOQyU5i0uSMwtzkyHS J1itOe4sm3vXmaOlYevAMndYHLTvq4DzEIsefl5qVLivBb3gNoEQNoySvPghsIS/iVGWSlhXk YGBgYhnoLUotzMElT5V4ziHIxKwrwBt4Gm8GTmlcDtfgV0FhPQWVKrw0DOKklESEk1MC1kzFl cq3BH+23A7Xzu1f6ROe2We8IPv3viZHSM+3zZl2Nvp7Bx199P/3R77i1+nVwO5ViHxW8z8icr Xpq34/jJbZe11i9btTFtFWeVxuHt2ziY0mrniKlXHDD8PF1p++KzhTtiS0RXOwYeuHJEYzb7Z DuZF49+55z7eti2U3iOVw7jwobNN5L/RPikzdgz66aZzMrz73PiXezVlFbkSN+o2rVzs05MeE Crv1rGB6uaV+Grz0eqMV+xYH5S2G0cpq0VdUpcIvJipqpU6IMpL7u5XLV4L/jMzWh6GCh49n/ rrOtntWu7WlRCRTo+Wm37ZNvJ2XtImXV77se+V0/X7S+etkuHNfeAleYdyVs5N5VYijMSDbWY i4oTAZkOzo1zBAAA X-Env-Sender: alanolya@invera.com X-Msg-Ref: server-3.tower-633.messagelabs.com!1717166037!1999!1 X-Originating-IP: [104.47.75.232] X-SYMC-ESS-Client-Auth: mailfrom-relay-check=pass X-StarScan-Received: X-StarScan-Version: 9.112.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14821 invoked from network); 31 May 2024 14:33:57 -0000 Received: from mail-yqbcan01lp2232.outbound.protection.outlook.com (HELO CAN01-YQB-obe.outbound.protection.outlook.com) (104.47.75.232) by server-3.tower-633.messagelabs.com with ECDHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 31 May 2024 14:33:57 -0000 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Pw0g07fkQsv7a57fvJfgIc5dmqOW8l2Zv6MsQumuCD5hFK+98cupIUfpgGupCPtLWlhVvmeLUBNoTYxKdy/wKUAE+IuFv5NjfIX5TYbPvHihGMx5IenOnkbBCd+2yHfXjxrlpuogBOUhymxkll00KhZjHxICS/N/J7QSHVbXBq/pR3qZwnTVh1gC7bc9j7sR79OhBDIlR1/vqduonCI3UA8Yn1sYvXWWTOuOXJKiLuuai8UojGRIa1ttpC+l7QPv3pnGFioo9abBn8nzlPEufjdTVCFC8hYr84Iq7Z8UWp2ML9NdTa1/BnskS9JHAAYZf8SybIG1Qys1o0jLA3ax7g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=SQ35lTMLRVXJUbOVD4oYFEXXRMc/dmo2LXO5yGAguvo=; b=Jb69kHCZyKyoZzC1KMKtM5Zl9Wk7QFGWmgzXTjOdHm748bNEUIewwRBHp0husAfzzIfkCFXVBB0oV7sTDbGrMlL/SlYnOHoAfznihDzP3V/Xez20LDNRr4XCDaumXmmMhxjH0MdjWQQv7quA5FTlahY9fjnfIKQOHEVlb+5LWQKvNb94V+h5ELt5a6Rb5AnX+pYGRu1d0hWYLVxp2KdxgzV+D7uTrQGzJUSsYwYfQp5KXXgsOL8pLdHGnnvaa5hf+Li8Sd/nEf1WyWQTxl03xxueeHL7qKKivUfVbPFCLeI/ljOjCX40qDfk4ktVFBjO5rPVaJGim1JFFyAAIKqZsA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=invera.com; dmarc=pass action=none header.from=invera.com; dkim=pass header.d=invera.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=invera.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=SQ35lTMLRVXJUbOVD4oYFEXXRMc/dmo2LXO5yGAguvo=; b=hEg1GW20SuB5lM2NxsWHFnbZ1vdGE8lwzXVKKgSpP0vzt71xE1t7hdwnFGzMcJW5DkroB29/8OEShr4A07fanm4aB5M0QZu0gYMDLahHkjGUa0whL04TdVGu+9TVmFjJw5Sjx2oTb49yRVGGSxz/bkB8J7CHXUgXuFPOMp/OlONjAMSWpNJam4Ju/M54GkkQCIc65bU1oOlS+D1UhKk+WrmjOdUSe3SvzFDSJ1yYNQNyzMAVEXze733q928Uxe8cIOMHQl2pqL+N1Hi4p2r4WZE/7VD14WL+991R2sG51nW1awxGGUdzOELF31ANJbuLn87CNVhLbROo0XIPFxfmNw== Received: from YQBPR01MB10625.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:c01:74::11) by YT1PR01MB9034.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:b01:cd::5) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7633.22; Fri, 31 May 2024 14:33:55 +0000 Received: from YQBPR01MB10625.CANPRD01.PROD.OUTLOOK.COM ([fe80::9201:c29d:e710:1173]) by YQBPR01MB10625.CANPRD01.PROD.OUTLOOK.COM ([fe80::9201:c29d:e710:1173%3]) with mapi id 15.20.7633.021; Fri, 31 May 2024 14:33:55 +0000 From: Alanoly Andrews To: Thom Brown CC: "pgsql-general@lists.postgresql.org" Subject: Re: ERROR: found xmin from before relfrozenxid; MultiXactid does no longer exist -- apparent wraparound Thread-Topic: ERROR: found xmin from before relfrozenxid; MultiXactid does no longer exist -- apparent wraparound Thread-Index: AQHasqGjm4w5GxWfhEWmBCq7Mox3vbGxBAoAgAAdbACAAEbNZg== Date: Fri, 31 May 2024 14:33:54 +0000 Message-ID: References: <4fbdd9760b329bccbdd62b6645d5977bee957e0d.camel@cybertec.at> In-Reply-To: Accept-Language: en-CA, en-US Content-Language: en-CA X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: x-ms-publictraffictype: Email x-ms-traffictypediagnostic: YQBPR01MB10625:EE_|YT1PR01MB9034:EE_ x-ms-office365-filtering-correlation-id: 65e050dd-ff28-4086-d223-08dc817eb316 x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0;ARA:13230031|366007|376005|1800799015|38070700009; x-microsoft-antispam-message-info: =?Windows-1252?Q?2l7LU3xL1OQPtmmHZA5iCdGxJRPul+Y6IPOP7mydhWti70hdEVP9Ex5G?= =?Windows-1252?Q?eEqlPi5X5x89Po6luDdkOF7mYXC2Ot74xfLfegRF1pABu8YVyXcg02Gx?= =?Windows-1252?Q?DQHvL50EoiTGCy1BqU08Lzrkt6yypEb99RC6/keKJDsLsUugyTD2y+Dc?= =?Windows-1252?Q?soZuA7TI0+Qi2JRiOdtzdRSoT7cIW548SKIVE6aBmmqaq3vZn+ctTYke?= =?Windows-1252?Q?6y7sOSLrwrICPfzQM6rer5jxNRiQgSXv5s6RMfpOOizD5c0aW/EWBiXf?= =?Windows-1252?Q?VnqPMMSePzA2qbjACSJcHBxdAe2Q/jaLC/sOpdoNqnui+4ApREkUMrmT?= =?Windows-1252?Q?/lJe6b2uRRF2l9+H/esTR4M9nrwdaJPMzGlUeGeN4PQN2U7mipAEgCdU?= =?Windows-1252?Q?tylgbHFTUuttXpC1r0Jq1t9akOUF9ymu5v8jvci5gBMKPjNOaCKrz15F?= =?Windows-1252?Q?lgksm4+cJlbZx8uBJ74tVsOvMpJRowVPV+FYXhpYp5henzxu3QyBQCk/?= =?Windows-1252?Q?i3n7MG65hQTgt9Ayw7GrYV1XUYSnMQNdqLEkg2D/Hwh4Ep/OM1tLavvL?= =?Windows-1252?Q?RuE10AZ6rDrYJo+XtYoow3z2BpQjApEMa2YVboK0ECVBa1Q8zsVmi5lj?= =?Windows-1252?Q?SGU3Yv/XQNjEP0lnDoeUbmD91bu+nS2PJbfYMne2JQP0OGpngXz7OZsN?= =?Windows-1252?Q?rN2QvAuP31kUoWUc3U/5jwu/GZklYeEWiA5ewPaXEUq+jcAEWicWH0F1?= =?Windows-1252?Q?2M3okSUy0RcVGrl5OABu4wQxHozJQR8JncoMwC1TkAyyoGNYO84j8iO6?= =?Windows-1252?Q?22lCn3j+qGr4mn25BHGb6Cqy+ZJAO2J7UT9vd5EYc+D+LvZ9TScWLYTl?= =?Windows-1252?Q?HH2r8k3D9ObNQ+trAlq+PNqb8TOcMxAhriNXd1oyYQ/4waECXVqvhT1Y?= =?Windows-1252?Q?K7xDiy3u8+oN45VZtTMGIi7o3Oi3vc7SPOFB1883QYIEd+Yohq0r05kh?= =?Windows-1252?Q?4YU+SKIMFfRiWPnzkKpLqxpnKo7glhD123/NJnZJ7m3jzgf1Qi8SNQZI?= =?Windows-1252?Q?ugm5RyYog8tEAeurHNaOANPD2icxFzmUSZ/R5VdjZO3cfyYdSo6K7ck1?= =?Windows-1252?Q?kx2ApG0rnnqqzft6bcDcuKlJ/8EuPhoXjFB01ORZR+TsxCu572gQvhFE?= =?Windows-1252?Q?rr5Ni2kappbKfRZW7rdLcoCeXMaTznWYWjR5Dt7soo0UDC8jl3CdR78+?= =?Windows-1252?Q?hB1PT2Df6ooqgkLq/+xOktG72VXESti2GuRtuVulAJVCvW4ynCTmIYkb?= =?Windows-1252?Q?JcWGIXEAYWJlOpYj1Ev5AIqRQwDjrRfPQUkNdPI/02wt+QIKKFklaQCR?= =?Windows-1252?Q?vPJ4KCDL5cgfP2i46H9q103Rhqzq0Iu58ToKm1DTQUtGQJDZblCyejQY?= =?Windows-1252?Q?hPrY0zZ3C4lvEjCPhamd3A=3D=3D?= x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:YQBPR01MB10625.CANPRD01.PROD.OUTLOOK.COM;PTR:;CAT:NONE;SFS:(13230031)(366007)(376005)(1800799015)(38070700009);DIR:OUT;SFP:1102; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?Windows-1252?Q?fGYpiX2b3rTBCG7UKGGqcnpCw1rdxtw9fEF5+Q1eHNVx9zu+z9lWCebu?= =?Windows-1252?Q?5kYqvdlFokZLCVtn81MGW3GRWK8SORimJ2gtOSNYbq9ETBvGUQpWjR+Y?= =?Windows-1252?Q?nBcP+TdZLXb0rl5irbUWqgCPSr1po87z3ljFgQyC1+aswR3qywlGX8oZ?= =?Windows-1252?Q?ZlQrCGOmlxzoYNvTMNueVmlQIIwlR2bNYoOm4NQz+3eTFtk15j6OYKPe?= =?Windows-1252?Q?dSTNO+q4TRt6x7+8z4Ac34aeXzrBVuIsLZa8hhpSGxp7oTD4YUG0+VjM?= =?Windows-1252?Q?F9ebKqywX8ReSprW7NpGBweQXxY3XuXchF0mnNj1++WnpyH9BilNgD8X?= =?Windows-1252?Q?9oexLmZhxX6jLMoj9W1vmp5rgarHG9WxF1K3nw+MTYHTcLsoPLKD5nau?= =?Windows-1252?Q?b40Uniztpk0sPRHPqvTaZ6vLARtUmV0dyFoS2yLlAOgXaNpjKhlEHYe0?= =?Windows-1252?Q?TiDIGQltpkO4C+0vC77uIIJH8/al/7wendv8Ti/+MpzKESEVD8fps2PQ?= =?Windows-1252?Q?6U3xoIDCkuxnr1KTnjuDtCYjRQJQVlqpiHGo7AMGfpsfHNIDQwRdKZVX?= =?Windows-1252?Q?AblyUKX1wyjBwJfUMJs/UyZV1uWHohZDdDDGt4Md3PyDWIP9sLbVubNq?= =?Windows-1252?Q?R0uxzwC/5methe0yOHnGNx7aWpFsufHJ3JBquQ5j2UBHWoKnYStIBECM?= =?Windows-1252?Q?U5KoDQ06bY9DPoVjKlBgAl96WI8TXBETj0wiLpM/Ll731iLHO5XvC6tV?= =?Windows-1252?Q?1ReaAuFXraUNVfQ6tzBj7sVWGWRuBXBztMM9sfZVBZcEc6MRqqDJdAxD?= =?Windows-1252?Q?fZJqF7P77NSoXY6pjd710fHxD7CjAd3VDlHH9w4/yhOSR2Ura8l+sW2I?= =?Windows-1252?Q?8Rf733tL0zY2mchyAdP8I95geetrX4+48wxqStSif9m0ctzJM8RPaWCi?= =?Windows-1252?Q?jg6Q9JGOshQuAy+92z5bWmMu8/EpDQ1dYzU4KTmyWe5+8oSXaDgyE9Nc?= =?Windows-1252?Q?v5AOvXvBkCI9oJ2ApZ3s/7Iz+HrAIJcoP+QzPKmLHdW2d5bwX1UcJzqg?= =?Windows-1252?Q?7nxUtS5cBPHpqJO68aNvWlAI2kMnnrlX95vC7QnZQMZFv48zbPx4zmP/?= =?Windows-1252?Q?k/5yzgulSZlmUSQhCmgwOAKOlEleHpgG7azcvpg/SK8SlZhUNgBLs67K?= =?Windows-1252?Q?9oEvDOXZi6Q7XlPDOPw6C6ZG7GrOuI287vRby/hXo2zU89jBf3ZQ0bZa?= =?Windows-1252?Q?A8msrYfnabaPXlfilnFLXm4s2wlbZ5kOWcVHjXQC/TTQF1+lBc91yfjS?= =?Windows-1252?Q?Cry58MXJT+P4jtFDAIZZOwymzWYs4y5pnCNWElZlmGXy4piNasNLDTl6?= =?Windows-1252?Q?4E6Fc/ckYhMyfWbwPnCUbBNVt5FlLXjG/rxUWxSB//Qs1b4TyNZGsENL?= =?Windows-1252?Q?3FZ+JPDsh37840pop6EPnQCThAzwCaQEIoCiCVk0/ICxzeDR1zZyd2cj?= =?Windows-1252?Q?KiApyxVJ0Pz07f4Jup2FW/C3cEH+WCUU2jD8npsSvKIm85XmJejG/ZQP?= =?Windows-1252?Q?GQlFRCp1RDLZdA/ME9VV7zoFqNIhGMs2OOgDvzH4IwaRpu37/sTPjWkd?= =?Windows-1252?Q?pSyFqTa9tRFUh/4n569uUurWDbGKn4y0sUjQQ7UCYJweGj5HtXFtGppm?= =?Windows-1252?Q?e49unLJDOY3ozijUdkmeQHvhhMn49cs/?= Content-Type: multipart/alternative; boundary="_000_YQBPR01MB106258258B8372A1ED0DA0648ABFC2YQBPR01MB10625CA_" MIME-Version: 1.0 X-OriginatorOrg: invera.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: YQBPR01MB10625.CANPRD01.PROD.OUTLOOK.COM X-MS-Exchange-CrossTenant-Network-Message-Id: 65e050dd-ff28-4086-d223-08dc817eb316 X-MS-Exchange-CrossTenant-originalarrivaltime: 31 May 2024 14:33:54.9894 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 63c603f5-415e-4e47-92ce-37fe9a1a475d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: p2c7wIEXcJJVQ0/5nH5DQFYPnXgIosESlpfaWw9VAWJAq4EBM4CzagCrbVERHv5RPr3Eh/JofLB0w2EGAQe/xQ== X-MS-Exchange-Transport-CrossTenantHeadersStamped: YT1PR01MB9034 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --_000_YQBPR01MB106258258B8372A1ED0DA0648ABFC2YQBPR01MB10625CA_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Thanks, Thom. I understand from your response that there is really no way to repair the c= urrent damage. Yes, we do take daily backups and we have, in fact, restored the database c= luster to a point in time before the corruption, suffering some loss of dat= a in the process. I'm now working with the snapshot of the corrupted databa= se (on a different box) to see if there is something that can be done to re= pair the damage and avoid such a scenario in future. Yes, and I know that = upgrading the Postgres version is the stock answer for situations like this= . The upgrade is in the works. But I was still interested in what the postgres gurus/programmers/hackers h= ad to say about this event. Regards. Alanoly. ________________________________ From: Thom Brown Sent: May 31, 2024 6:14 AM To: Laurenz Albe Cc: Alanoly Andrews ; pgsql-general@lists.postgresql.o= rg Subject: Re: ERROR: found xmin from before relfrozenxid; MultiXactid does n= o longer exist -- apparent wraparound You don't often get email from thom@linux.com. Learn why this is important<= https://aka.ms/LearnAboutSenderIdentification> [Email External/Externe] Caution opening links or attachments/attention lor= s de l'ouverture de liens ou de pi=E8ces jointes. On Fri, May 31, 2024, 09:29 Laurenz Albe > wrote: On Thu, 2024-05-30 at 14:58 +0000, Alanoly Andrews wrote: > We have a postgres 10.7 database which reports a number of issues on user= -created > tables as well as system tables. Most errors are one of the following: > -- ERROR: found xmin 1888159934 from before relfrozenxid 1998177448 > -- ERROR: MultiXactId 613819197 does no longer exist -- apparent wraparo= und > -- ERROR: could not access status of transaction 1927393975 > DETAIL: Could not open file "pg_xact/072E": No such file or directory= . > > Is there a way to repairing the corruption in this database? > Postgres Version 10.7 on Linux(Ubuntu). Perhaps, but you should hire an expert if the data are important for you. Also, while it's too late now, this could be the result of a bug in the ver= sion you are using that was subsequently repaired in 10.15: Prevent possible data loss from concurrent truncations of SLRU logs (Noah M= isch) This rare problem would manifest in later =93apparent wraparound=94 or =93c= ould not access status of transaction=94 errors. This is why it's important to keep up-to-date, but even the latest minor 10= .x release is out of date as support was dropped back in 2022. If you manage to get this up and running again, I strongly recommend upgrad= ing to the latest major and minor release (16.3 at the time of writing). Before you try doing anything though, create a physical backup of your data= base as situations like this tend to require invasive action that could pot= entially make the situation even worse. Also, did this problem only happen in the last day or two? How frequently d= o you take backups? If you have a backup from just before this issue starti= ng showing itself, and you can afford losing data changes that have occured= since the backup, you may find it far easier and quicker to resort to usin= g that backup. Of course, you would need to prove to yourself that the back= up was safe by running a VACUUM FREEZE on each database in that backup befo= re starting to use it. If that runs without issue, you're probably in the = clear. Best of luck. Thom This e-mail may be privileged and/or confidential, and the sender does not = waive any related rights and obligations. Any distribution, use or copying = of this e-mail or the information it contains by other than an intended rec= ipient is unauthorized. If you received this e-mail in error, please advise= me (by return e-mail or otherwise) immediately. Ce courriel est confidentiel et prot=E9g=E9. L'exp=E9diteur ne renonce pas = aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation = ou copie de ce message ou des renseignements qu'il contient par une personn= e autre que le (les) destinataire(s) d=E9sign=E9(s) est interdite. Si vous = recevez ce courriel par erreur, veuillez m'en aviser imm=E9diatement, par r= etour de courriel ou par un autre moyen.'. --_000_YQBPR01MB106258258B8372A1ED0DA0648ABFC2YQBPR01MB10625CA_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Thanks, Thom.
I understand from your response that there is really no way to repair the c= urrent damage. 

Yes, we do take daily backups and we have, in fact, restored the database c= luster to a point in time before the corruption, suffering some loss of dat= a in the process. I'm now working with the snapshot of the corrupted databa= se (on a different box) to see if there is something that can be done to repair the damage and avoid such a = scenario in future.  Yes, and I know that upgrading the Postgres versi= on is the stock answer for situations like this. The upgrade is in the= works.

But I was still interested in what the postgres gurus/programmers/hackers h= ad to say about this event.

Regards.
Alanoly.
From: Thom Brown <thom@l= inux.com>
Sent: May 31, 2024 6:14 AM
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Alanoly Andrews <alanolya@invera.com>; pgsql-general@lists= .postgresql.org <pgsql-general@lists.postgresql.org>
Subject: Re: ERROR: found xmin from before relfrozenxid; MultiXactid= does no longer exist -- apparent wraparound
 
You don't often get email from thom@linux.com. Learn why this is important

[Email External/Externe] Caution opening links or attac= hments/attention lors de l'ouverture de liens ou de pi=E8ces jointes.

On Fri, May 31, 2024, 09:29 Laurenz= Albe <laurenz.albe@cybertec= .at> wrote:
On Thu, 2024-05-30 at 14:58 +0000, Alanoly Andrews wrote:
> We have a postgres 10.7 database which reports a number of issues on u= ser-created
> tables as well as system tables. Most errors are one of the following:=
> -- ERROR:  found xmin 1888159934 from before relfrozenxid 1998177= 448
> -- ERROR:  MultiXactId 613819197 does no longer exist -- apparent= wraparound
> -- ERROR:  could not access status of transaction 1927393975
>    DETAIL:  Could not open file "pg_xact/072E"= ;: No such file or directory.
>
> Is there a way to repairing the corruption in this database?
> Postgres Version 10.7 on Linux(Ubuntu).

Perhaps, but you should hire an expert if the data are important for you.

Also, while it's too late now, this could be the result o= f a bug in the version you are using that was subsequently repaired in 10.1= 5:

Prevent possible data loss from concurrent truncations of= SLRU logs (Noah Misch)

This rare problem would manifest in later =93apparent wra= paround=94 or =93could not access status of transaction=94 errors.

This is why it's important to keep up-to-date, but even t= he latest minor 10.x release is out of date as support was dropped back in = 2022.

If you manage to get this up and running again, I strongl= y recommend upgrading to the latest major and minor release (16.3 at the ti= me of writing).

Before you try doing anything though, create a physical b= ackup of your database as situations like this tend to require invasive act= ion that could potentially make the situation even worse.

Also, did this problem only happen in the last day or two= ? How frequently do you take backups? If you have a backup from just before= this issue starting showing itself, and you can afford losing data changes= that have occured since the backup, you may find it far easier and quicker to resort to using that backup. Of = course, you would need to prove to yourself that the backup was safe by run= ning a VACUUM FREEZE on each database in that backup before starting to use= it.  If that runs without issue, you're probably in the clear.

Best of luck.

Thom

This e-mail may be privileged and/or confidential, and the sender does n= ot waive any related rights and obligations. Any distribution, use or copyi= ng of this e-mail or the information it contains by other than an intended = recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or other= wise) immediately.


Ce courriel est confidentiel et prot=E9g=E9. L'exp=E9diteur ne renonce p= as aux droits et obligations qui s'y rapportent. Toute diffusion, utilisati= on ou copie de ce message ou des renseignements qu'il contient par une pers= onne autre que le (les) destinataire(s) d=E9sign=E9(s) est interdite. Si vous recevez ce courriel par erreur, veui= llez m'en aviser imm=E9diatement, par retour de courriel ou par un autre mo= yen.'.

--_000_YQBPR01MB106258258B8372A1ED0DA0648ABFC2YQBPR01MB10625CA_--