Re: HeapTupleData.t_self garbage values

Поиск
Список
Период
Сортировка
Искать
От
Kevin Grittner
Тема
Re: HeapTupleData.t_self garbage values
Дата
Msg-id
4B98FF75020000250002FC9E@gw.wicourts.gov
Ответ на
Список
Дерево обсуждения
HeapTupleData.t_self garbage values "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: HeapTupleData.t_self garbage values Tom Lane <tgl@sss.pgh.pa.us>
Re: HeapTupleData.t_self garbage values "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: HeapTupleData.t_self garbage values Tom Lane <tgl@sss.pgh.pa.us>
Re: HeapTupleData.t_self garbage values "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: HeapTupleData.t_self garbage values Tom Lane <tgl@sss.pgh.pa.us>
Re: HeapTupleData.t_self garbage values "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Tom Lane  wrote:
> "Kevin Grittner"  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

В списке pgsql-hackers по дате отправления
От: Tom Lane
Дата:
От: Greg Stark
Дата:
FAQ