diff options
| author | Etsuro Fujita <efujita@postgresql.org> | 2024-04-11 19:05:07 +0900 |
|---|---|---|
| committer | Etsuro Fujita <efujita@postgresql.org> | 2024-04-11 19:05:07 +0900 |
| commit | 0341d4b10e786dcbc4c63da9d21af842ab31e118 (patch) | |
| tree | 867462b18f3bfa3ec192434f4913aef5728f299c /src/backend/executor/nodeModifyTable.c | |
| parent | 5e9d8bed0094b146d64013d417c51eb0f69aeafd (diff) | |
| download | postgresql-0341d4b10e786dcbc4c63da9d21af842ab31e118.tar.gz postgresql-0341d4b10e786dcbc4c63da9d21af842ab31e118.zip | |
Fix WaitEventSet resource leak in WaitLatchOrSocket().
This function would have the same issue we solved in commit 501cfd07d:
If an error is thrown after calling CreateWaitEventSet(), the file
descriptor (on epoll- or kqueue-based systems) or handles (on Windows)
that the WaitEventSet contains are leaked.
Like that commit, use PG_TRY-PG_FINALLY (PG_TRY-PG_CATCH in v12) to make
sure the WaitEventSet is freed properly.
Back-patch to all supported versions, but as we do not have this issue
in HEAD (cf. commit 50c67c201), no need to apply this patch to it.
Discussion: https://postgr.es/m/CAPmGK16MqdDoD8oatp8SQWaEa4vS3nfQqDN_Sj9YRuu5J3Lj9g%40mail.gmail.com
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions