Hi, If a DSM is created or attached from an interrupt handler while a transaction is being rolled back, it may result in the following error. "ResourceOwnerEnlarge called after release started" This was found during the testing of Enhancing Memory Context Reporting feature by Fujii Masao [1].
I propose a fix to fall back to creating a DSM or DSA with a NULL resource owner if CurrentResourceOwner is set to "releasing". Since a DSM or DSA can already be created with a NULL resource owner— meaning it persists for the lifetime of the backend or until explicitly detached— this approach should be acceptable. Please find attached a patch which does that. Kindly let me know your views. [1]. https://www.postgresql.org/message-id/a1a7e2b7-8f33-4313-baff-42e92ec14fd3%40oss.nttdata.com <https://www.postgresql.org/message-id/a1a7e2b7-8f33-4313-baff-42e92ec14fd3%40oss.nttdata.com>
0001-Prevent-the-error-on-creating-a-dsm-segment-from-an-.patch
Description: Binary data
