From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: dyuzenn98@gmail.com
Subject: BUG #18099: ERROR: could not access status of transaction 4007513275
Date: Fri, 08 Sep 2023 06:36:20 +0000
Message-ID: <18099-cb4ffa6e2874d039@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 18099
Logged by: Dogukan Yuzen
Email address: dyuzenn98@gmail.com
PostgreSQL version: 14.8
Operating system: Red Hat Enterprise Linux Server release 7.9 (Maipo
Description:
A few days ago , we had some problems in our production database.
We can't read the table.
We can't solve this problem.
ERROR: could not access status of transaction 4007513275
DETAIL: Could not open file "pg_xact/0EED": No such file or directory.
Please, help us.
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, dyuzenn98@gmail.com
Subject: Re: BUG #18099: ERROR: could not access status of transaction 4007513275
In-Reply-To: <18099-cb4ffa6e2874d039@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