Thread: BUG #18099: ERROR: could not access status of transaction 4007513275
BUG #18099: ERROR: could not access status of transaction 4007513275
From
PG Bug reporting form
Date:
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.
Em 08/09/2023 03:36, PG Bug reporting form escreveu:
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.
Try to remove all files stored in pg_twophase directory and than restart the service. I had similar situation and doing that, solved the problem.
Somethimes, old prepared transactios can cause this problem and removing the files of pg_twophase should fix.
best regards,
---
![]() | Carlos Alves Especialista ![]() Sia Trecho 08, lotes 245 / 255 / 265 || +55 (61) 3039-9700 71205-080 || Guará || Brasília, DF 0800-6020097 www.tecnisys.com.br |
Attachment
On Fri, 2023-09-08 at 06:36 +0000, PG Bug reporting form wrote: > 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. That's data corruption. Restore your backup. What is your proof that this was caused by a PostgreSQL software bug? More frequent causes are hardware problems or pilot error (pg_resetwal or other manipulations that break your database). Yours, Laurenz Albe