On Wed, Oct 1, 2008 at 2:54 PM, Tom Lane <[EMAIL PROTECTED]> wrote: > So it seems like the appropriate generalization is to have an array of > read positions inside the tuplestore and allow callers to say "read > using position N", plus some API to allow positions to be allocated to > different requestors. We could get rid of the separate mark pointer by > implementing an API that allows position X to be copied to position Y. > But the actual value of a position (a tuple number or file position > info) would never be exposed to callers.
That's basicaly what had done (though i had n "readers" which encapsulated the current pointer and mark). One other reason the tuplestore should know the position of all the readers is that ideally it would want to be able to discard any tuples older than the oldest read position. That also means it needs to know when all the call sites have allocated their position and don't need to reset it. -- greg -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
