Hi On August 22, 2019 9:14:10 AM PDT, Dilip Kumar <dilipbal...@gmail.com> wrote: > But, those requests will >ultimately be used for collecting the record by the bulk fetch. So if >we are planning to change the bulk fetch to read forward then maybe we >don't need the valid last undo record pointer because that we will >anyway get while processing forward. So just knowing the end of the >transaction is sufficient for us to know where to stop. I am not sure >if this solution has any problem. Probably I should think again in >the morning when my mind is well-rested.
I don't think we can easily do so for bulk apply without incurring significant overhead. It's pretty cheap to read in forward order and then process backwards on a page level - but for an entire transactions undo the story is different. We can't necessarily keep all of it in memory, so we'd have to read the undo twice to find the end. Right? Andres Andres Andres -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
