Re: ERROR: attempted to delete invisible tuple

From: Bryan Murphy <bmurphy1976(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Greg Stark <gsstark(at)mit(dot)edu>, pgsql-general(at)postgresql(dot)org
Subject: Re: ERROR: attempted to delete invisible tuple
Date: 2009-08-17 18:30:31
Message-ID: 7fd310d10908171130g2934ebc7y1950fa64d2ed2fd0@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Aug 17, 2009 at 12:41 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Bryan Murphy <bmurphy1976(at)gmail(dot)com> writes:
> > On Mon, Aug 17, 2009 at 12:17 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> Hm, what's your current XID counter? (pg_controldata would give an
> >> approximate answer.) I'm wondering if the xmax's are marked committed
> >> but are in the future ...
>
> > Latest checkpoint's NextXID: 0/308829887
>
> Hmm, well, they're in the past *now*, but by less than 20000
> transactions. You said this was a production DB so that might not
> represent very much elapsed time. Does the DELETE still fail?
>
> regards, tom lane
>

Wow, how crazy is that. I was just able to delete those three records. I
tried the remaining, and two were left that I could delete. Waited 30
seconds, tried again and now they're gone as well. As far as I'm aware,
that's all the bad records in that table.

The database went down last Weds. How could they have gotten that far into
the future?

Bryan

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Josh Kupershmidt 2009-08-17 18:43:55 Re: Pgbench tool download
Previous Message Adrian Klaver 2009-08-17 18:23:42 Re: plpython return setof and yield