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

From Bryan Murphy
Subject Re: ERROR: attempted to delete invisible tuple
Date
Msg-id 7fd310d10908171020r7bad9628u7efa57c2772ec523@mail.gmail.com
Whole thread Raw
In response to Re: ERROR: attempted to delete invisible tuple  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ERROR: attempted to delete invisible tuple  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Mon, Aug 17, 2009 at 12:17 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
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

postgres@domU-12-31-36-00-38-C1:~$ /usr/lib/postgresql/8.3/bin/pg_controldata /srv/pg_data/8.3/main/
pg_control version number:            833
Catalog version number:               200711281
Database system identifier:           5184368167085382525
Database cluster state:               in production
pg_control last modified:             Mon 17 Aug 2009 05:16:50 PM UTC
Latest checkpoint location:           B4A/45E0DE38
Prior checkpoint location:            B4A/3690AC00
Latest checkpoint's REDO location:    B4A/36929DF0
Latest checkpoint's TimeLineID:       5
Latest checkpoint's NextXID:          0/308829887
Latest checkpoint's NextOID:          26030968
Latest checkpoint's NextMultiXactId:  5958225
Latest checkpoint's NextMultiOffset:  40968054
Time of latest checkpoint:            Mon 17 Aug 2009 04:56:38 PM UTC
Minimum recovery ending location:     A17/C6D9A98
Maximum data alignment:               8
Database block size:                  8192
Blocks per segment of large relation: 131072
WAL block size:                       8192
Bytes per WAL segment:                16777216
Maximum length of identifiers:        64
Maximum columns in an index:          32
Maximum size of a TOAST chunk:        1996
Date/time type storage:               64-bit integers
Maximum length of locale name:        128
LC_COLLATE:                           en_US.UTF-8

Thanks,
Bryan 

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: ERROR: attempted to delete invisible tuple
Next
From: Chris Bowlby
Date:
Subject: Re: pg_autovacuum exceptions question