mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-10-04 05:26:50 +02:00
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 practice in any case. Add the info to the HINT, not the ERROR string, so as not to change the regression tests' expected output.
This commit is contained in:
parent
5e8b7b0b73
commit
6736916f5f
@ -3021,8 +3021,9 @@ check_stack_depth(void)
|
|||||||
ereport(ERROR,
|
ereport(ERROR,
|
||||||
(errcode(ERRCODE_STATEMENT_TOO_COMPLEX),
|
(errcode(ERRCODE_STATEMENT_TOO_COMPLEX),
|
||||||
errmsg("stack depth limit exceeded"),
|
errmsg("stack depth limit exceeded"),
|
||||||
errhint("Increase the configuration parameter \"max_stack_depth\", "
|
errhint("Increase the configuration parameter \"max_stack_depth\" (currently %dkB), "
|
||||||
"after ensuring the platform's stack depth limit is adequate.")));
|
"after ensuring the platform's stack depth limit is adequate.",
|
||||||
|
max_stack_depth)));
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user