-
dirty buffer and datafile?
when checkpoint occurs , dirty buffers are written to datafile.
it means that datfile contains both commited and uncommited data.
when commit occurs block may not be in db buffer cache on that time
how database handles the block/transaction?.
how long that uncommited data will be stored in datafile? if it is not going to contain uncommited data for
long time(till commit occurs) is it not overhead for database to contain both commited and uncommited?
J Gangadhar
-
Re: dirty buffer and datafile?
Originally posted by ganga
when checkpoint occurs , dirty buffers are written to datafile.
it means that datfile contains both commited and uncommited data.
when commit occurs block may not be in db buffer cache on that time
how database handles the block/transaction?.
how long that uncommited data will be stored in datafile? if it is not going to contain uncommited data for
long time(till commit occurs) is it not overhead for database to contain both commited and uncommited?
imagine the other way around write to the datafile whenever a commit occurs..so that the datafile contains only comitted transactions..now what do u think whil will be more overhead :-)
regards
Hrishy
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|