Skip site navigation (1) Skip section navigation (2)

Re: SSI error messages

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SSI error messages
Date: 2011-07-29 18:46:20
Message-ID: 1311965180.768.6.camel@vanquo.pezone.net (view raw or flat)
Thread:
Lists: pgsql-hackers
On lör, 2011-07-16 at 21:55 +0300, Heikki Linnakangas wrote:
> I think I would prefer something like this:
> 
> ERROR:  could not serialize access due to read/write dependencies
> among 
> transactions
> DETAIL: Reason code: %s
> HINT:  The transaction might succeed if retried.
> 
> Where %s gets the current detail field, untranslated, like:
> 
> Canceled on commit attempt with conflict in from prepared pivot.

Do you have an idea how to address this case:

@@ -3865,7 +3865,7 @@ CheckForSerializableConflictOut(bool visible, Relation relation,
                ereport(ERROR,
                        (errcode(ERRCODE_T_R_SERIALIZATION_FAILURE),
                         errmsg("could not serialize access due to read/write dependencies among transactions"),
-                        errdetail_internal("Canceled on conflict out to old pivot %u.", xid),
+                        errdetail("Reason code: %s.", "canceled on conflict out to old pivot %u", xid),  // XXX bogus
                      errhint("The transaction might succeed if retried.")));
 
            if (SxactHasSummaryConflictIn(MySerializableXact)


In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2011-07-29 18:59:09
Subject: Re: include host names in hba error messages
Previous:From: Peter EisentrautDate: 2011-07-29 18:44:15
Subject: Re: include host names in hba error messages

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group