diff options
| author | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2023-07-05 13:13:13 +0300 |
|---|---|---|
| committer | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2023-07-05 13:13:39 +0300 |
| commit | 59c2a6fe9b6518255d99a6bbf9006a98a0aefa6b (patch) | |
| tree | 9784a3d47adbc5a4b24b1d4d8ee5747df0c7323e /src/backend/commands/dbcommands.c | |
| parent | acc8cdff424529ce34e93a7ae51eb410b02c7b30 (diff) | |
| download | postgresql-59c2a6fe9b6518255d99a6bbf9006a98a0aefa6b.tar.gz postgresql-59c2a6fe9b6518255d99a6bbf9006a98a0aefa6b.zip | |
Fix leak of LLVM "fatal-on-oom" section counter.
llvm_release_context() called llvm_enter_fatal_on_oom(), but was missing
the corresponding llvm_leave_fatal_on_oom() call. As a result, if JIT was
used at all, we were almost always in the "fatal-on-oom" state.
It only makes a difference if you use an extension written in C++, and
run out of memory in a C++ 'new' call. In that case, you would get a
PostgreSQL FATAL error, instead of the default behavior of throwing a
C++ exception.
Back-patch to all supported versions.
Reviewed-by: Daniel Gustafsson
Discussion: https://www.postgresql.org/message-id/54b78cca-bc84-dad8-4a7e-5b56f764fab5@iki.fi
Diffstat (limited to 'src/backend/commands/dbcommands.c')
0 files changed, 0 insertions, 0 deletions