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

Re: Table has duplicate keys, what did I do

From: John Gateley <gateley(at)jriver(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Table has duplicate keys, what did I do
Date: 2008-01-29 18:13:16
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-general
On Tue, 29 Jan 2008 12:53:11 -0500
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> John Gateley <gateley(at)jriver(dot)com> writes:
> > Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> John Gateley <gateley(at)jriver(dot)com> writes:
> >>> Somehow I have managed to have two tables with duplicate keys.
> >> What PG version is this?  We've fixed some bugs in the past that
> >> could give rise to duplicated rows.
> > Currently 8.1.4, and it's been tracking Ubuntu 6.06 LTS for
> > updates, so it could have been earlier than 8.1.4 when the duplicate
> > row actually was created.
> There was a fix released in 8.1.9 for a problem that could cause VACUUM
> FULL to create duplicate copies of a row that had recently been updated.
> Does that sound like a plausible scenario for your usage?

Yes, it does, very much so. The row in question is updated once
a minute (it is "test" data that is used by our system monitor
to ensure that the database is up, and one of the tests is updating
the row), and the database is vacuumed full once a day.



John Gateley <gateley(at)jriver(dot)com>

In response to


pgsql-general by date

Next:From: Joshua D. DrakeDate: 2008-01-29 18:16:44
Subject: Re: postgresql book - practical or something newer?
Previous:From: Willem BuitendykDate: 2008-01-29 18:11:38
Subject: Analyze Explanation

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