> On 1 May 2025, at 14:40, Robert Haas <robertmh...@gmail.com> wrote:
> ..in general I'm > skeptical that we can really set up something that is OK to do in an > aborted transaction, because our ability to handle any further errors > at that point is extremely limited, and this code is definitely > complex enough that it could error out. Rahila and I were talking about this last week at PGConf.dev and one safety measure to implement here is to skip this processing for aborted transactions. While there will be cases when debugging the memory of an aborted transaction is of interest, we are as you say limited in what we can/should do in that case so immediately returning is the safer option. The attached also encodes the example from this thread as a test using an interactive background. (The attached has a small context id fix as well but the interesting bit is the above.) -- Daniel Gustafsson
0001-Avoid-memory-context-reporting-in-aborted-transactio.patch
Description: Binary data
