On 14 March 2013 08:56, Emmanuel Lécharny <elecha...@gmail.com> wrote: > Le 3/13/13 4:39 PM, Emmanuel Lécharny a écrit : >> One small update, as I have made a mistake in my initial mail : >> >> >> It's not implemented atm, will work on that. >> >> Any better idea ? > > I rethought about the proposal this morning, and found it over complex. > > A better idea is to store an offset to the BTree headers in a list of > BTree offsets, at the beginning of the file. If this list of offset > can't be stored in a single page, we will use a new page to store the > overflowing offsets. Adding or removing a BTree will just be a matter of > adding or removing an offset from this list (which might require a > rewrite of those pages. > Thoughts ?
Seems to me that the currently proposed solutions all depend on the disk blocks being updated in a specific sequence. Depending on the hardware/OS/language being used, AFAIK this may not be possible to enforce. May I suggest that any assumptions about the behaviour of the host disk system should be clearly documented? --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscr...@labs.apache.org For additional commands, e-mail: labs-h...@labs.apache.org
