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

Re: BUG #1242: Major bug in pgSQL

From: Gaetano Mendola <mendola(at)bigfoot(dot)com>
To: PostgreSQL Bugs List <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #1242: Major bug in pgSQL
Date: 2004-09-07 13:35:58
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
PostgreSQL Bugs List wrote:

> Problem: in some cases we experience the following problem - we have found 
> in the database some _absolutely_ identical rows, despite the fact, that we 
> have defined some unique (!) indexes on some of the fields and even primary 
> (!) keys, we can see, that the rows are _exactly_ the same. In some cases we 
> have seen up to 7 absolutely identical rows, with the same primary keys and 
> the same unique indexed fields. 

I had the same experiences in 7.3 release and I realized that this is due to
some interaction between vacuum, reindex and update on the same table. See
this posts:

unfortunatelly I never was able to reproduce it.

When you are experiencing this show us the result of this query:

select cmax, cmin, xmax, xmin, * from <table> where <your condition>;

where <your condition> is a filter in order to obtain the rows wit the
primary key duplicated.

However I'm sure that you don't have two row with duplicated primary
key but two version of the same row, the result however is the same.

Are you reindexing your tables regulary ?

Gaetano Mendola

In response to


pgsql-bugs by date

Next:From: Tom LaneDate: 2004-09-07 14:05:01
Subject: Re: BUG #1242: Major bug in pgSQL
Previous:From: emilDate: 2004-09-07 13:33:38
Subject: The server closes connetion without reason -3.

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