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: | 20080129121316.a2192234.gateley@jriver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
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.
Thanks,
j
--
John Gateley <gateley(at)jriver(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2008-01-29 18:16:44 | Re: postgresql book - practical or something newer? |
Previous Message | Willem Buitendyk | 2008-01-29 18:11:38 | Analyze Explanation |