Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> Would it be helpful to do this for duplicate row detection as well?
> It would be great to get the htids of the two duplicates when we do
> detect this situation.
99.999% of the time it would be confusing gibberish :-(. That's a very
ordinary user-facing error message, remember.
If we had a way to know that a particular occurrence represented a
(seemingly) internal problem rather than run-of-the-mill user error,
then yeah, but I don't see how we'd know that.
regards, tom lane
In response to
pgsql-committers by date
|Next:||From: User Rlucas||Date: 2008-01-01 02:46:55|
|Subject: aupg - aupg_src: changed the set_current_sw_actor function not to depend |
|Previous:||From: Simon Riggs||Date: 2007-12-31 18:10:32|
|Subject: Re: pgsql: Improve a number of elog messages fornot-supposed-to-happen|