Subject | Re: [IB-Architect] Super-transactions and Incremental Backup |
---|---|
Author | Jim Starkey |
Post date | 2000-06-22T14:57:33Z |
At 06:22 PM 6/21/00 -0700, you wrote:
structure) is center around fixed length pages which are read and
written atomically. Database pages and operation system pages are
quite different things.
disk I/O, only mapped files. Rather than simplifying database
implementation, in fact it made it more complex. From time to
time operation system geeks come up with the recurring idea of
a single level store -- no files, no directories, just a very
large, flat virtual space. Horrible concept.
Jim Starkey
>Could you elaborate, please?
>In my mind I don't see where deleted and limbo records would be a problem.
>They just seem to fit in with all the rest of the stuff.
>
>It has very little to do with OS paging. The database ODS (on disk
>Is the paging architecture still valid in todays OS and hardware
>environments? To me at least, I wonder if perhaps operating systems aren't
>advanced enough such that the whole paging scheme can just be left up to the
>OS.
>
structure) is center around fixed length pages which are read and
written atomically. Database pages and operation system pages are
quite different things.
>Feel free to flame me but please understand that I do not know OS's at allThe Apollo operation system, Domain, had no concept whatsoever of
>when programming at these levels. I would be very interested in hearing how
>these layers come into play when dealing with reading and writing
>information in the file system. I would also like to know the feasibility of
>creating a database system that off-loaded the complexity of paging totally
>to the OS.
>
disk I/O, only mapped files. Rather than simplifying database
implementation, in fact it made it more complex. From time to
time operation system geeks come up with the recurring idea of
a single level store -- no files, no directories, just a very
large, flat virtual space. Horrible concept.
>I think perhaps the first thing I am going to hear is that with a crossWorks for me.
>platform database being able to abstract this layer makes things much
>simpler. Let's put that aside if we can for the sake of discussion. Jim's
>replies would be nice but let's not all get into the habit of simply waiting
>to see what Jim has to say, ok?
>
Jim Starkey