On Mon, Aug 21, 2017 at 12:58 PM, Haribabu Kommi <kommi.harib...@gmail.com> wrote: > > On Sun, Aug 13, 2017 at 5:17 PM, Amit Kapila <amit.kapil...@gmail.com> > wrote: >> >> >> Also, it is quite possible that some of the storage Am's don't even >> want to return bool as a parameter from HeapTupleSatisfies* API's. I >> guess what we need here is to provide a way so that different storage >> am's can register their function pointer for an equivalent to >> satisfies function. So, we need to change >> SnapshotData.SnapshotSatisfiesFunc in some way so that different >> handlers can register their function instead of using that directly. >> I think that should address the problem you are planning to solve by >> omitting buffer parameter. > > > Thanks for your suggestion. Yes, it is better to go in the direction of > SnapshotSatisfiesFunc. > > I verified the above idea of implementing the Tuple visibility functions > and assign them into the snapshotData structure based on the snapshot. > > The Tuple visibility functions that are specific to the relation are > available > with the RelationData structure and this structure may not be available, >
Which functions are you referring here? I don't see anything in tqual.h that uses RelationData. -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
