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

From Simon Riggs
Subject Re: pgsql: Improve a number of elog messages for not-supposed-to-happen
Date
Msg-id 1199124632.9558.189.camel@ebony.site
Whole thread Raw
In response to pgsql: Improve a number of elog messages for not-supposed-to-happen  (tgl@postgresql.org (Tom Lane))
Responses Re: pgsql: Improve a number of elog messages for not-supposed-to-happen  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
On Mon, 2007-12-31 at 04:52 +0000, Tom Lane wrote:

> Log Message:
> -----------
> Improve a number of elog messages for not-supposed-to-happen cases in btrees,
> since these seem to happen after all in corrupted indexes.  Make sure we
> supply the index name in all cases, and provide relevant block numbers where
> available.  Also consistently identify the index name as such.
>
> Back-patch to 8.2, in hopes that this might help Mason Hale figure out his
> problem.

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.

--
  Simon Riggs
  2ndQuadrant  http://www.2ndQuadrant.com


pgsql-committers by date:

Previous
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Provide a more helpful error message when there is an autoconf
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Improve a number of elog messages for not-supposed-to-happen