Re: ERROR: attempted to delete invisible tuple - Mailing list pgsql-general

From Tom Lane
Subject Re: ERROR: attempted to delete invisible tuple
Date
Msg-id 3721.1250529428@sss.pgh.pa.us
Whole thread Raw
In response to Re: ERROR: attempted to delete invisible tuple  (Bryan Murphy <bmurphy1976@gmail.com>)
Responses Re: ERROR: attempted to delete invisible tuple  (Bryan Murphy <bmurphy1976@gmail.com>)
Re: ERROR: attempted to delete invisible tuple  (Greg Stark <gsstark@mit.edu>)
Re: ERROR: attempted to delete invisible tuple  (Greg Stark <gsstark@mit.edu>)
List pgsql-general
Bryan Murphy <bmurphy1976@gmail.com> writes:
> Here's the xmin/xmax/ctid for three problematic records:

> prodpublic=# select xmin,xmax,ctid from items_extended where id in
> ('34537ed90d7546d78f2c172fc8eed687', '3e1d99b7124742b7aaf2f869f7637b0e',
> '499b464f141a48619c5ce0475cbe9150');
>    xmin    |   xmax    |    ctid
> -----------+-----------+------------
>  262232659 | 308810030 | (689496,3)
>  262629744 | 308810034 | (692765,1)
>  262643188 | 308810035 | (692920,9)
> (3 rows)

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 ...

            regards, tom lane

pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pg_autovacuum exceptions question
Next
From: Bryan Murphy
Date:
Subject: Re: ERROR: attempted to delete invisible tuple