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:13 +0300 |
commit | 4f4d73466d71976b58f29121bab9d9fef6f3436e (patch) | |
tree | 1735f70e91c9bbd2c980ef82048f536948450dd7 /src/fe_utils/string_utils.c | |
parent | 088539015173a204839a53d1d0fc8fa8c96783ba (diff) | |
download | postgresql-4f4d73466d71976b58f29121bab9d9fef6f3436e.tar.gz postgresql-4f4d73466d71976b58f29121bab9d9fef6f3436e.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/fe_utils/string_utils.c')
0 files changed, 0 insertions, 0 deletions