Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m8LSs-00066V-E0 for pgsql-bugs@arkaria.postgresql.org; Tue, 27 Jul 2021 11:41:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1m8LSr-000128-D5 for pgsql-bugs@arkaria.postgresql.org; Tue, 27 Jul 2021 11:41:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m8LPm-00046k-J0 for pgsql-bugs@lists.postgresql.org; Tue, 27 Jul 2021 11:38:26 +0000 Received: from email.ftc.ru ([194.85.126.43]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m8LPj-0004Ny-HK for pgsql-bugs@lists.postgresql.org; Tue, 27 Jul 2021 11:38:26 +0000 Received: from mail.cft.ru (nut-exch-3.ftc.ru [172.29.95.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail-gate-2.ftc.ru (Postfix) with ESMTPS id 676602C0C10 for ; Tue, 27 Jul 2021 18:38:20 +0700 (+07) DKIM-Filter: OpenDKIM Filter v2.11.0 mail-gate-2.ftc.ru 676602C0C10 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cft.ru; s=relay; t=1627385900; bh=StF31i32ZZ7c5Ksii0Eu038Fp6l1IuZB4iL1EezmAnc=; h=From:To:Subject:Date:Message-ID:From:Sender:To:CC:Subject: Message-Id:Date; b=rHrgEvIBwhmuo3pL5t1+yPNVfJ2JkOYm/wvoJtyZ/SUa/zG24/GXVWegrPq0nSPdK 4qrcrCma3UYWCA9Tq+TXFvOshfHVJb7ezCZmxPsne8pJTKd5Gb9ceBZARYiyyRE9zk 3gfvDOdErpvCowBALHRONT47DbZDvuJgnefQrFIY= Received: from nut-exch-1.win.ftc.ru (172.29.95.118) by nut-exch-1.win.ftc.ru (172.29.95.118) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.858.15; Tue, 27 Jul 2021 18:38:20 +0700 Received: from nut-exch-1.win.ftc.ru ([fe80::eca3:338b:8a83:2440]) by nut-exch-1.win.ftc.ru ([fe80::eca3:338b:8a83:2440%5]) with mapi id 15.02.0858.015; Tue, 27 Jul 2021 18:38:20 +0700 From: Orishich Aleksey To: "pgsql-bugs@lists.postgresql.org" Subject: RE: Postgresql12: ERROR: Could not read from file "pg_act/02 F 4" at offset 253952: read too few bytes Thread-Topic: Postgresql12: ERROR: Could not read from file "pg_act/02 F 4" at offset 253952: read too few bytes Thread-Index: Add4W/xNfkxl7v0tR+iRna69jnUYEAKf8wVg Date: Tue, 27 Jul 2021 11:38:20 +0000 Message-ID: <44f273afed1e4ba3ba75b056eb65e829@cft.ru> References: <909f68c697ab4d45a10ea6fc5957d1a5@cft.ru> In-Reply-To: <909f68c697ab4d45a10ea6fc5957d1a5@cft.ru> Accept-Language: ru-RU, en-US Content-Language: ru-RU X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.94.8] Content-Type: multipart/alternative; boundary="_000_44f273afed1e4ba3ba75b056eb65e829cftru_" MIME-Version: 1.0 X-KLMS-Rule-ID: 1 X-KLMS-Message-Action: clean X-KLMS-AntiSpam-Lua-Profiles: 165268 [Jul 27 2021] X-KLMS-AntiSpam-Version: 5.9.20.0 X-KLMS-AntiSpam-Envelope-From: a.orishich@cft.ru X-KLMS-AntiSpam-Rate: 0 X-KLMS-AntiSpam-Status: not_detected X-KLMS-AntiSpam-Method: none X-KLMS-AntiSpam-Auth: dkim=none X-KLMS-AntiSpam-Info: LuaCore: 449 449 5db59deca4a4f5e6ea34a93b13bc730e229092f4, {Tracking_b2b_test_cert_from_list}, {Tracking_from_domain_doesnt_match_to}, mail.cft.ru:7.1.1;127.0.0.199:7.1.2;cft.ru:7.1.1;d41d8cd98f00b204e9800998ecf8427e.com:7.1.1 X-MS-Exchange-Organization-SCL: -1 X-KLMS-AntiSpam-Interceptor-Info: scan successful X-KLMS-AntiPhishing: Clean, bases: 2021/07/27 10:45:00 X-KLMS-AntiVirus: Kaspersky Security for Linux Mail Server, version 8.0.3.30, bases: 2021/07/27 08:46:00 #16963359 X-KLMS-AntiVirus-Status: Clean, skipped List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --_000_44f273afed1e4ba3ba75b056eb65e829cftru_ Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Hello. Do you have a result on my problem? This is critical for us. From: Orishich Aleksey Sent: Wednesday, July 14, 2021 10:03 AM To: pgsql-bugs@lists.postgresql.org Subject: [MASSMAIL] Postgresql12: ERROR: Could not read from file "pg_act/0= 2 F 4" at offset 253952: read too few bytes Hello. While the postgres database was running, we encountered the following error= : ERROR: could not access status of transaction 793754117 Detail: Could not r= ead from file "pg_act/02 F 4" at offset 253952: read too few bytes. The pg_act/02 F 4 file on the main database had a different size from other= files. At the same time, the pg_xact/02F4 file on the backup database had = a standard size of 256Kb. There are no errors writing to the file system. N= o errors were found in the postgres logs either. After this error occurred, working with the main database was impossible, a= nd we had to switch to the backup database. What could have caused this error in postgres? Was it possible to restore t= he database without switching to a backup? How can I prevent such errors fr= om occurring in the future? How to correctly troubleshooting the cause of t= his error? Postgres version: 12.1-2 OS: Oracle Linux Server release 7.6 With Regards, Aleksey. --_000_44f273afed1e4ba3ba75b056eb65e829cftru_ Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable

Hello.

 

Do you have a result on my prob= lem? This is critical for us.

&n= bsp;

&n= bsp;

From: Orishich Aleksey <a.oris= hich@cft.ru>
Sent: Wednesday, July 14, 2021 10:03 AM
To: pgsql-bugs@lists.postgresql.org
Subject: [MASSMAIL] Postgresql12: ERROR: Could not read from file &q= uot;pg_act/02 F 4" at offset 253952: read too few bytes

 

Hello.

 

While the postgres database was= running, we encountered the following error:

ERROR: could not access status = of transaction 793754117 Detail: Could not read from file "pg_act/02 F= 4" at offset 253952: read too few bytes.

The pg_act/02 F 4 file on the m= ain database had a different size from other files. At the same time, the p= g_xact/02F4 file on the backup database had a standard size of 256Kb. There= are no errors writing to the file system. No errors were found in the postgres logs either.

After this error occurred, work= ing with the main database was impossible, and we had to switch to the back= up database.

What could have caused this err= or in postgres? Was it possible to restore the database without switching t= o a backup? How can I prevent such errors from occurring in the future? How= to correctly troubleshooting the cause of this error?

Postgres version: 12.1-2

OS: Oracle Linux Server release= 7.6

 

With Regards,

Aleksey.

--_000_44f273afed1e4ba3ba75b056eb65e829cftru_--