Re: [GENERAL] How duplicate data produce when a UNIQUE index exite ? - Mailing list pgsql-bugs

From Scott Marlowe
Subject Re: [GENERAL] How duplicate data produce when a UNIQUE index exite ?
Date
Msg-id dcc563d10911242243s48c8b657m12ea16608e57d4b8@mail.gmail.com
Whole thread Raw
Responses Re: [GENERAL] How duplicate data produce when a UNIQUE index exite ?
答复: [GENERAL] How duplicate data produce when a UNIQUE index exite ?
List pgsql-bugs
2009/11/24 RD黄永卫 <yongwei_huang@gtmc.com.cn>:
> Dear all,
>
>
>
> When   "reindex" operation do,this error occurred:
> Nov 22 10:22:27 SUC11 postgres[14145]: [2-1] ERROR:  could not create unique
> index
> Nov 22 10:22:27 SUC11 postgres[14145]: [2-2] DETAIL:  Table contains
> duplicated values.
> Nov 22 10:22:27 SUC11 postgres[14145]: [2-3] STATEMENT:  REINDEX TABLE
> "t_sfh_history"
>
> My question is:
>
> How the  Duplicate datas produce when a UNIQUE index exite ?
> Is this a bug of PostgreSQL ?

Either bad hardware, or a pgsql bug can do this.

> My postgreSQL version is :
>  PostgreSQL 8.1.4 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2.3
> 20030502 (Red Hat Linux 3.2.3-56)

You are aware that 8.1.x is up to 8.1.18, right, that's 14 or so
updates you're missing.  Could one of them have fixed a bug that
causes this? Sure.  Look through the changelogs to be sure, but why
not just keep your pgsql version up to date?  It's easier.

Or are you running some redhat version that stays the same number
while getting bugs back ported to it or something?

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #5212: incorrect resource manager data checksum in record at ...
Next
From: Scott Marlowe
Date:
Subject: Re: 答复: [GENERAL] How duplicate data produce when a UNIQUE index exite ?