aboutsummaryrefslogtreecommitdiff
path: root/src/tutorial
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2023-07-05 13:13:13 +0300
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2023-07-05 13:13:30 +0300
commitfa96a74a0f76c49ac5a43a16fca8bf705fa98d99 (patch)
treebeb39066a8c6b7a8e86d28ea9181e13e5dd07bfa /src/tutorial
parent66f8a139731957a7d516ade70cd3aa43d12d3c4f (diff)
downloadpostgresql-fa96a74a0f76c49ac5a43a16fca8bf705fa98d99.tar.gz
postgresql-fa96a74a0f76c49ac5a43a16fca8bf705fa98d99.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/tutorial')
0 files changed, 0 insertions, 0 deletions