pgsql: Include the current value of max_stack_depth in stack depth comp

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Include the current value of max_stack_depth in stack depth comp
Date: 2010-11-04 21:16:01
Message-ID: E1PE7A9-0008JM-5r@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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(-)

Browse pgsql-committers by date

  From Date Subject
Next Message User Jbcooley 2010-11-06 00:25:30 npgsql - Npgsql2: Updating for new release
Previous Message Tom Lane 2010-11-04 20:34:58 pgsql: Allow moddatetime's target column to be of type timestamptz.