Re: BUG #16961: Could not access status of transaction

Alexandra Wang <alexandra.wang.oss@gmail.com>

From: Alexandra Wang <alexandra.wang.oss@gmail.com>

To: Daniil Davydov <3danissimo@gmail.com>

Cc: noah@leadboat.com, Tom Lane <tgl@sss.pgh.pa.us>, Stepan Yankevych <Stepan_Yankevych@epam.com>, Stepan Yankevych <stepya@ukr.net>, "sergii.zhuravlev@smartnet.ua" <sergii.zhuravlev@smartnet.ua>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>, Shruthi Gowda <gowdashru@gmail.com>

Date: 2025-08-01T03:50:42Z

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

Forgot to paste the reference link:

[1]
https://www.postgresql.org/message-id/18804-bccbbde5e77a68c2%40postgresql.org

PS: To reproduce the bug, you must first disconnect any backend
listening on the channel (backend 1 in Andrei Varashen's repro) before
registering the new listener that triggers the error.

Best,
Alex

>