From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bryan Murphy <bmurphy1976(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: ERROR: attempted to delete invisible tuple |
Date: | 2009-08-17 17:50:39 |
Message-ID: | 407d949e0908171050r7fe7b17k4f7d5ab5b18f7148@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Aug 17, 2009 at 6:17 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Bryan Murphy <bmurphy1976(at)gmail(dot)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)
Hm, perhaps I should have asked for xvac as well, as that can also
trigger an "invisible" status. You can't select xvac directly but if
you query cmin it might be possible to tell what's going on.
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2009-08-17 18:01:30 | Re: ERROR: attempted to delete invisible tuple |
Previous Message | Bob Gobeille | 2009-08-17 17:46:12 | Re: psql command line editor |