From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: ev.yanchuk.s@gmail.com
Subject: BUG #17528: ERROR: could not access status of transaction 1997627701
Date: Wed, 22 Jun 2022 05:34:58 +0000
Message-ID: <17528-1df379cdbc43ea7b@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 17528
Logged by: Evgeniy Yanchuk
Email address: ev.yanchuk.s@gmail.com
PostgreSQL version: 10.19
Operating system: CentOS Linux release 7.7.1908 (Core)
Description:
Hello.
I've found on our server (PostgreSQL 10.19 on x86_64-pc-linux-gnu, compiled
by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit)
2022-06-21 09:08:08.291 MSK [34331:44/99061] [u178-01] [local]
10.201.14.125:10081 : Check.Finish ERROR: could not access status of
transaction 1997627701
2022-06-21 09:08:08.291 MSK [34331:44/99061] [u178-01] [local]
10.201.14.125:10081 : Check.Finish DETAIL: Could not open file
"pg_xact/0771": No such file or directory.
2022-06-21 09:08:08.291 MSK [34331:44/99061] [u178-01] [local]
10.201.14.125:10081 : Check.Finish STATEMENT:
I created the file "pg_xact/0771" using the command "dd if=/dev/zero
of=/var/lib/pgsql/10/data/pg_xact/0771 bs=256k count=1", but the error
reappeared after a while.
Restarting postgresql.service didn't help either.
Thanks, Evgeniy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, ev.yanchuk.s@gmail.com
Subject: Re: BUG #17528: ERROR: could not access status of transaction 1997627701
In-Reply-To: <17528-1df379cdbc43ea7b@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox