pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18099: ERROR: could not access status of transaction 4007513275
3+ messages / 3 participants
[nested] [flat]
* BUG #18099: ERROR: could not access status of transaction 4007513275
@ 2023-09-08 06:36 PG Bug reporting form <noreply@postgresql.org>
2023-09-08 15:18 ` Re: BUG #18099: ERROR: could not access status of transaction 4007513275 Carlos Alves <carlos.alves@tecnisys.com.br>
2023-09-08 17:45 ` Re: BUG #18099: ERROR: could not access status of transaction 4007513275 Laurenz Albe <laurenz.albe@cybertec.at>
0 siblings, 2 replies; 3+ messages in thread
From: PG Bug reporting form @ 2023-09-08 06:36 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: dyuzenn98@gmail.com
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.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: BUG #18099: ERROR: could not access status of transaction 4007513275
2023-09-08 06:36 BUG #18099: ERROR: could not access status of transaction 4007513275 PG Bug reporting form <noreply@postgresql.org>
@ 2023-09-08 15:18 ` Carlos Alves <carlos.alves@tecnisys.com.br>
1 sibling, 0 replies; 3+ messages in thread
From: Carlos Alves @ 2023-09-08 15:18 UTC (permalink / raw)
To: dyuzenn98@gmail.com; pgsql-bugs@lists.postgresql.org; +Cc: PG Bug reporting form <noreply@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
* Re: BUG #18099: ERROR: could not access status of transaction 4007513275
2023-09-08 06:36 BUG #18099: ERROR: could not access status of transaction 4007513275 PG Bug reporting form <noreply@postgresql.org>
@ 2023-09-08 17:45 ` Laurenz Albe <laurenz.albe@cybertec.at>
1 sibling, 0 replies; 3+ messages in thread
From: Laurenz Albe @ 2023-09-08 17:45 UTC (permalink / raw)
To: dyuzenn98@gmail.com; pgsql-bugs@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2023-09-08 17:45 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-09-08 06:36 BUG #18099: ERROR: could not access status of transaction 4007513275 PG Bug reporting form <noreply@postgresql.org>
2023-09-08 15:18 ` Carlos Alves <carlos.alves@tecnisys.com.br>
2023-09-08 17:45 ` Laurenz Albe <laurenz.albe@cybertec.at>
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