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-08-15 12:27:46 |
Message-ID: | 1313411266.9614.22.camel@vanquo.pezone.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
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.
I've done it this way now, except that "Reason code" is not marked for
translation, for the implementation reasons discussed downthread.
I'm looking forward to see how many of these we'll see in practice and
how users will react to them.
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-08-15 13:37:54 | Re: synchronized snapshots |
Previous Message | Robert Haas | 2011-08-15 11:52:21 | Re: Online base backup from the hot-standby |