pgsql: Include the current value of max_stack_depth in stack depth comp - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Include the current value of max_stack_depth in stack depth comp
Date
Msg-id E1PE7A9-0008JM-5r@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
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.

Branch
------
master

Details
-------
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=6736916f5f5a5f340aa20d4b27540764b5646585

Modified Files
--------------
src/backend/tcop/postgres.c |    5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Allow moddatetime's target column to be of type timestamptz.
Next
From: jbcooley@pgfoundry.org (User Jbcooley)
Date:
Subject: npgsql - Npgsql2: Updating for new release