hi,is it dangerous to only use tuple pointer through heap_getnext()? - Mailing list pgsql-general

From sunpeng
Subject hi,is it dangerous to only use tuple pointer through heap_getnext()?
Date
Msg-id AANLkTinff2aMXWjv4Y4WADcNShyiV8mm-ibjI-rqmVln@mail.gmail.com
Whole thread Raw
Responses Re: hi,is it dangerous to only use tuple pointer through heap_getnext()?  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-general
hi,i use these codes to store only pointer of tuple :
HeapTuple *tuple;
    tuple = heap_getnext(pHeapScanDesc,ForwardScanDirection);
    while(tuple){
        //[1#]here i only store the pointer of tuple in an array for later using,that means i don't retrive attribute data from this tuple ,is this ok?
        myArray[i++]=tuple;
        //then next tuple
        tuple = heap_getnext(pHeapScanDesc,ForwardScanDirection);
    }
at place [1#],i only store the pointer of current tuple in an array for later using,that means i don't retrieve attribute data from this tuple ,is this ok?
could these tuple pointers be invalid sometimes later if myArray still reference these tuples? i know these tuples have been read into buffers in shared memory, yet I am not sure wether these buffers be replaced or marked invalid when myArray still points to these tuples in according buffers.
thanks a lot!

peng

pgsql-general by date:

Previous
From: Joao Ferreira gmail
Date:
Subject: Re: autovacuum: 50% iowait for hours
Next
From: Alvaro Herrera
Date:
Subject: Re: hi,is it dangerous to only use tuple pointer through heap_getnext()?