From: tgl@postgresql.org
To: pgsql-committers@postgresql.org
Subject: pgsql: Fix GUC's reports of assign_hook failure to always include the
Date: Thu, 2 Apr 2009 03:51:43 +0000 (UTC)
Message-ID: <20090402035143.B2B17754ADE@cvs.postgresql.org> (raw)
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)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@postgresql.org
Subject: Re: pgsql: Fix GUC's reports of assign_hook failure to always include the
In-Reply-To: <20090402035143.B2B17754ADE@cvs.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox