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

Commit6736916

Browse files
committed
Include the current value of max_stack_depth in stack depth complaints.
I'm mainly interested in finding out what it is on buildfarm machines,but including the active value in the message seems like good practicein any case. Add the info to the HINT, not the ERROR string, so as notto change the regression tests' expected output.
1 parent5e8b7b0 commit6736916

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

‎src/backend/tcop/postgres.c

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3021,8 +3021,9 @@ check_stack_depth(void)
30213021
ereport(ERROR,
30223022
(errcode(ERRCODE_STATEMENT_TOO_COMPLEX),
30233023
errmsg("stack depth limit exceeded"),
3024-
errhint("Increase the configuration parameter \"max_stack_depth\", "
3025-
"after ensuring the platform's stack depth limit is adequate.")));
3024+
errhint("Increase the configuration parameter \"max_stack_depth\" (currently %dkB), "
3025+
"after ensuring the platform's stack depth limit is adequate.",
3026+
max_stack_depth)));
30263027
}
30273028
}
30283029

0 commit comments

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