pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Carlos Alves <carlos.alves@tecnisys.com.br>
To: dyuzenn98@gmail.com
To: pgsql-bugs@lists.postgresql.org
Cc: PG Bug reporting form <noreply@postgresql.org>
Subject: Re: BUG #18099: ERROR:  could not access status of transaction 4007513275
Date: Fri, 08 Sep 2023 12:18:33 -0300
Message-ID: <ba3a12ee7b3579d1d81e13f783357c2c@tecnisys.com.br> (raw)
In-Reply-To: <18099-cb4ffa6e2874d039@postgresql.org>
References: <18099-cb4ffa6e2874d039@postgresql.org>

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 [1] 

 

Links:
------
[1] http://www.tecnisys.com.br

Attachments:


f62593aa.gif (image/gif, 43B) download
  view image



04237a95.gif (image/gif, 3.1K) download
  view image

view thread (3+ messages)  latest in thread

Message-ID: <ba3a12ee7b3579d1d81e13f783357c2c@tecnisys.com.br>
Permalink:  ../ba3a12ee7b3579d1d81e13f783357c2c@tecnisys.com.br/
Also on:    postgresql.org/message-id/ba3a12ee7b3579d1d81e13f783357c2c@tecnisys.com.br

 · 

reply
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: carlos.alves@tecnisys.com.br, dyuzenn98@gmail.com, pgsql-bugs@lists.postgresql.org, noreply@postgresql.org
  Subject: Re: BUG #18099: ERROR:  could not access status of transaction 4007513275
  In-Reply-To: <ba3a12ee7b3579d1d81e13f783357c2c@tecnisys.com.br>

* 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