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

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

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)postgresql(dot)org>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Improve a number of elog messages fornot-supposed-to-happen
Date: 2007-12-31 18:10:32
Message-ID: 1199124632.9558.189.camel@ebony.site (view raw or flat)
Thread:
Lists: 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


In response to

Responses

pgsql-committers by date

Next:From: Tom LaneDate: 2007-12-31 18:20:58
Subject: Re: pgsql: Improve a number of elog messages for not-supposed-to-happen
Previous:From: Bruce MomjianDate: 2007-12-31 17:28:31
Subject: pgsql: Provide a more helpful error message when there is an autoconf

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