Re: Another WaitEventSet resource leakage in back branches
Etsuro Fujita <etsuro.fujita@gmail.com>
From: Etsuro Fujita <etsuro.fujita@gmail.com>
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-04-05T10:55:16Z
Lists: pgsql-hackers
Attachments
- fix-another-WaitEventSet-resource-leakage.patch (application/octet-stream) patch
- fix-another-WaitEventSet-resource-leakage-PG12.patch (application/octet-stream) patch
On Fri, Mar 22, 2024 at 9:15 PM Etsuro Fujita <etsuro.fujita@gmail.com> wrote: > While working on [1], I noticed $SUBJECT: WaitLatchOrSocket in back > branches is ignoring the possibility of failing partway through, too. > I added a PG_FAINALLY block to that function, like commit 555276f85. > Patch attached. I noticed that PG_FAINALLY was added in v13. I created a separate patch for v12 using PG_CATCH instead. Patch attached. I am attaching the previous patch for later versions as well. I am planning to back-patch these next week. Best regards, Etsuro Fujita
Commits
-
Fix WaitEventSet resource leak in WaitLatchOrSocket().
- 0341d4b10e78 12.19 landed
- 01b01a77fe78 13.15 landed
- b714bc40cf06 14.12 landed
- b82dca2a5a92 15.7 landed
- e79ceafe93a8 16.3 landed
-
Fix resource leak when a FDW's ForeignAsyncRequest function fails
- 555276f85940 14.11 cited