Re: ERROR: attempted to delete invisible tuple
| От | Greg Stark |
|---|---|
| Тема | Re: ERROR: attempted to delete invisible tuple |
| Дата | |
| Msg-id | 407d949e0908171101p59ef5489p51f0cfa793e2b27d@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: ERROR: attempted to delete invisible tuple (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: ERROR: attempted to delete invisible tuple
|
| Список | pgsql-general |
On Mon, Aug 17, 2009 at 6:17 PM, Tom Lane<tgl@sss.pgh.pa.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 ... > FWIW that doesn't look right. That would result in HeapTupleBeingUpdated. The only case where it could result in "invisible" is if it's our own xid. Excluding the cases where our own xid is in the tuple I think the relevant cases are either xmin aborted or in progress (or in future) MOVED_OFF and xvac committed MOVED_IN and xvac aborted or is in progress (or in future) -- greg http://mit.edu/~gsstark/resume.pdf
В списке pgsql-general по дате отправления: