Re: HeapTupleData.t_self garbage values

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: HeapTupleData.t_self garbage values
Date: 2010-03-11 20:34:29
Message-ID: 4B98FF75020000250002FC9E@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
>> According to htup.h:
>> * t_self and t_tableOid should be valid if the HeapTupleData
>> * points to a disk buffer, or if it represents a copy of a tuple
>> * on disk. They should be explicitly set invalid in manufactured
>> * tuples.
>
>> In the heap_hot_search_buffer function of heapam.c this is not
>> true.

> What that comment is recommending is
>
> ItemPointerSetInvalid(&(tuple.t_self));

Aren't those tuples pointing to a disk buffer? I know how to set an
invalid pointer, but I thought that was only for manufactured
tuples?

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2010-03-11 20:35:48 Re: [patch] build issues on Win32
Previous Message Tom Lane 2010-03-11 20:25:17 Re: HeapTupleData.t_self garbage values