RE: BUG #16961: Could not access status of transaction
Stepan Yankevych <stepan_yankevych@epam.com>
From: Stepan Yankevych <Stepan_Yankevych@epam.com>
To: Stepan Yankevych <stepya@ukr.net>,
"sergii.zhuravlev@smartnet.ua" <sergii.zhuravlev@smartnet.ua>,
"pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Cc: "sergii.zhuravlev@smartnet.ua" <sergii.zhuravlev@smartnet.ua>
Date: 2021-04-19T18:49:15Z
Lists: pgsql-bugs
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix bug where we truncated CLOG that was still needed by LISTEN/NOTIFY
- eba917d360e7 14.21 landed
- 1a469d7b5b7d 15.16 landed
- 053e1868b7ee 16.12 landed
- d02c03ddc5e3 17.8 landed
- 321ec54625fd 18.2 landed
- 8eeb4a0f7c06 19 (unreleased) landed
The database was rebooted and the issue disappeared Hopefully it was one time issue. From: Stepan Yankevych <stepya@ukr.net> Sent: Wednesday, April 14, 2021 7:12 PM To: sergii.zhuravlev@smartnet.ua; pgsql-bugs@lists.postgresql.org Cc: sergii.zhuravlev@smartnet.ua Subject: Re: BUG #16961: Could not access status of transaction Hi Guys! Let me clarify few things things about the issue. The issue happening each morning when application starts on the production DataBase during about a month. Always the same transaction id is mentioned in the error (1954017648) We tried to do UNLISTEN - no changes. the same issue. LISTEN works good for any other channels. Can it be related to some hanged transaction? 1954017648? (for example while some network interruption) Is it possible to kill/clean it somehow without DB restart? Can it be related to some non-vacuumed system table or so? Any other ideas? Thanks! --- Original message --- From: "PG Bug reporting form" <noreply@postgresql.org<mailto:noreply@postgresql.org>> Date: 13 April 2021, 18:50:26 The following bug has been logged on the website: Bug reference: 16961 Logged by: Sergey Zhuravlev Email address: sergii.zhuravlev@smartnet.ua<mailto:sergii.zhuravlev@smartnet.ua> PostgreSQL version: 13.2 Operating system: CentOS Linux release 7.9.2009 (Core) Description: Hello Command - LISTEN missed_trades_empty_instrument " ERROR: could not access status of transaction 1954017648 DETAIL: Could not open file "pg_xact/0747": No such file or directory. STATEMENT: LISTEN missed_trades_empty_instrument " Current transaction # select txid_current(); txid_current -------------- 6985716158 Parameter - autovacuum_freeze_max_age = 200000000