Lomet, D., Salzberg, B., "Performance of Multiversion Data," Proc. SIGMOD 1990, Atlantic City, pp. 353-363.  Home/Search   Document Not in Database   Summary   Related Articles

....is only one copy of current data in POSTGRES; it is in the current database. No logs are kept in this model; it is assumed that no media (stable main memory) failures will occur. Our recent work [LoSa5] on versioned backups combines the functionality of a full temporal index, the Time Split B tree [LoSa1, LoSa2] or TSB tree with that of a fuzzy image copy of the database. Thus, with very little overhead beyond that ordinarily required for making a backup, both temporal queries and media recovery can be supported. 1.2 Index Concurrency Our second major area of work [LoSa6] is that of index concurrency. ....

....by time, the versions of records which span the split time have copies in both nodes, as illustrated in Figure 1. This allows for a locality of reference for as of or snapshot queries asking for a picture of the database as it was at a certain time in the past, but it creates some redundancy. [LoSa2] analyzed the extent of that redundancy. 2.2 Use of TSB tree for Media Recovery We have modified the TSB tree to use it for media recovery. It needed modification in order to guarantee that there is a copy in the backup of every current record which has been changed since the last backup. In ....

Lomet, D., Salzberg, B., "Performance of Multiversion Data," Proc. SIGMOD 1990, Atlantic City, pp. 353-363.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC