diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2010-11-04 17:15:38 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2010-11-04 17:15:38 -0400 |
| commit | 6736916f5f5a5f340aa20d4b27540764b5646585 (patch) | |
| tree | ada19ee79719ed5238f8b199b523b386d036b33c /src/backend/tcop/postgres.c | |
| parent | 5e8b7b0b73b6d0aba4a5a05704601dd031ad0a49 (diff) | |
| download | postgresql-6736916f5f5a5f340aa20d4b27540764b5646585.tar.gz postgresql-6736916f5f5a5f340aa20d4b27540764b5646585.zip | |
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.
Diffstat (limited to 'src/backend/tcop/postgres.c')
| -rw-r--r-- | src/backend/tcop/postgres.c | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/src/backend/tcop/postgres.c b/src/backend/tcop/postgres.c index cba90a9e727..edf18fd0f20 100644 --- a/src/backend/tcop/postgres.c +++ b/src/backend/tcop/postgres.c @@ -3021,8 +3021,9 @@ check_stack_depth(void) ereport(ERROR, (errcode(ERRCODE_STATEMENT_TOO_COMPLEX), errmsg("stack depth limit exceeded"), - errhint("Increase the configuration parameter \"max_stack_depth\", " - "after ensuring the platform's stack depth limit is adequate."))); + errhint("Increase the configuration parameter \"max_stack_depth\" (currently %dkB), " + "after ensuring the platform's stack depth limit is adequate.", + max_stack_depth))); } } |