Re: ERROR: Cannot insert a duplicate key into unique index - Mailing list pgsql-general

From Bruce Momjian
Subject Re: ERROR: Cannot insert a duplicate key into unique index
Date
Msg-id 200401100339.i0A3drJ26769@candle.pha.pa.us
Whole thread Raw
In response to Re: ERROR: Cannot insert a duplicate key into unique index pg_class_relname_nsp_index  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Tom Lane wrote:
> >> Digging in the 7.3.2-to-7.3.4 change logs, I see one potentially
> >> relevant change:
>
> > The only thing I can think of is the fix for splitting the first btree
> > page.
>
> I paused on that too, but I don't see how it could apply, unless they
> were dropping and rebuilding their database every few hours.  Besides,
> that bug is fixed in 7.3.5, which is still showing the problem.

I didn't know we got that into 7.3.5, but now I remember it wasn't
serious enough to force a new 7.3.X release but it was in 7.3.X CVS.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: ERROR: Cannot insert a duplicate key into unique index pg_class_relname_nsp_index
Next
From: Tom Lane
Date:
Subject: Re: Postgres planner bug in 7.3.x and 7.4.1 ?