BUG #17528: ERROR: could not access status of transaction 1997627701

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: ev(dot)yanchuk(dot)s(at)gmail(dot)com
Subject: BUG #17528: ERROR: could not access status of transaction 1997627701
Date: 2022-06-22 05:34:58
Message-ID: 17528-1df379cdbc43ea7b@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 17528
Logged by: Evgeniy Yanchuk
Email address: ev(dot)yanchuk(dot)s(at)gmail(dot)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

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2022-06-22 13:53:56 Re: BUG #17526: PG_DUMP is not outputting "CREATE SCHEMA" statements when an extension is assigned to a schema
Previous Message Noah Misch 2022-06-22 03:37:04 Re: Extension pg_trgm, permissions and pg_dump order