pgsql: Fix GUC's reports of assign_hook failure to always include the

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix GUC's reports of assign_hook failure to always include the
Date: 2009-04-02 03:51:43
Message-ID: 20090402035143.B2B17754ADE@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Fix GUC's reports of assign_hook failure to always include the parameter value
we failed to assign, even in "can't happen" cases. Motivated by wondering
what's going on in a recent trouble report where "failed to commit" did
happen.

Modified Files:
--------------
pgsql/src/backend/utils/misc:
guc.c (r1.497 -> r1.498)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/guc.c?r1=1.497&r2=1.498)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2009-04-02 03:51:50 pgsql: Fix GUC's reports of assign_hook failure to always include the
Previous Message Tom Lane 2009-04-02 01:16:25 pgsql: plpgsql's exec_simple_cast_value() mistakenly supposed that it