Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit162aa47

Browse files
committed
Fix leak of LLVM "fatal-on-oom" section counter.
llvm_release_context() called llvm_enter_fatal_on_oom(), but was missingthe corresponding llvm_leave_fatal_on_oom() call. As a result, if JIT wasused 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++, andrun out of memory in a C++ 'new' call. In that case, you would get aPostgreSQL FATAL error, instead of the default behavior of throwing aC++ exception.Back-patch to all supported versions.Reviewed-by: Daniel GustafssonDiscussion:https://www.postgresql.org/message-id/54b78cca-bc84-dad8-4a7e-5b56f764fab5@iki.fi
1 parent1b4f1c6 commit162aa47

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

‎src/backend/jit/llvm/llvmjit.c

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -233,6 +233,8 @@ llvm_release_context(JitContext *context)
233233

234234
pfree(jit_handle);
235235
}
236+
237+
llvm_leave_fatal_on_oom();
236238
}
237239

238240
/*

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp