Re: ERROR: Cannot insert a duplicate key into unique index

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Kragen Sitaker <kragen+pgsql(at)airwave(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: ERROR: Cannot insert a duplicate key into unique index
Date: 2004-01-10 03:39:53
Message-ID: 200401100339.i0A3drJ26769@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Doug McNaught 2004-01-10 04:46:21 Re: Query string is too long
Previous Message Tom Lane 2004-01-10 03:32:22 Re: ERROR: Cannot insert a duplicate key into unique index pg_class_relname_nsp_index