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

From: Alexandra Wang <alexandra(dot)wang(dot)oss(at)gmail(dot)com>
To: Daniil Davydov <3danissimo(at)gmail(dot)com>
Cc: noah(at)leadboat(dot)com, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stepan Yankevych <Stepan_Yankevych(at)epam(dot)com>, Stepan Yankevych <stepya(at)ukr(dot)net>, "sergii(dot)zhuravlev(at)smartnet(dot)ua" <sergii(dot)zhuravlev(at)smartnet(dot)ua>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Shruthi Gowda <gowdashru(at)gmail(dot)com>
Subject: Re: BUG #16961: Could not access status of transaction
Date: 2025-08-01 03:50:42
Message-ID: CAK98qZ0u+oTD67BkA9Adgw2_qBkDAmdvqZP65bAsHsDv+rgxiw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Amit Kapila 2025-08-01 04:33:14 Re: Use-after-free in reorderbuffer.c for INSERT ON CONFLICT
Previous Message Alexandra Wang 2025-08-01 03:41:17 Re: BUG #16961: Could not access status of transaction