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

Commitd379659

Browse files
committed
Further fix thinko in plpgsql memory leak fix.
There's a second call of get_eval_mcontext() that should also beget_stmt_mcontext(). This is actually dead code, since nointeresting allocations happen before switching back to theoriginal context, but we should keep it in sync with the othercall to forestall possible future bugs.Discussion:https://postgr.es/m/f075f7be-c654-9aa8-3ffc-e9214622f02a@enterprisedb.com
1 parentfd1347f commitd379659

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

‎src/pl/plpgsql/src/pl_exec.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2259,7 +2259,7 @@ exec_stmt_call(PLpgSQL_execstate *estate, PLpgSQL_stmt_call *stmt)
22592259
row->varnos= (int*)palloc(sizeof(int)*list_length(funcargs));
22602260

22612261
if (!local_plan)
2262-
MemoryContextSwitchTo(get_eval_mcontext(estate));
2262+
MemoryContextSwitchTo(get_stmt_mcontext(estate));
22632263

22642264
/*
22652265
* Examine procedure's argument list. Each output arg position

0 commit comments

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