Re: pgsql: Improve a number of elog messages for not-supposed-to-happen

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Improve a number of elog messages for not-supposed-to-happen
Date: 2007-12-31 18:20:58
Message-ID: 7605.1199125258@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-committers

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

Browse pgsql-committers by date

  From Date Subject
Next Message User Rlucas 2008-01-01 02:46:55 aupg - aupg_src: changed the set_current_sw_actor function not to depend
Previous Message Simon Riggs 2007-12-31 18:10:32 Re: pgsql: Improve a number of elog messages fornot-supposed-to-happen