Micah Acinapura
DBMS

7.7 When a request is made for a page, if it's in the pool the pin count is
increased by one. If its not in the pool, the buffer manager must make space for it 
if the pool is full, once there is space the buffer manager increments the pin count, sets the dirty bit to zero and reads the page into the selected frame.

7.8 A page is written to disk when the frame it's being stored in has been chosen
for replacement and if the dirty bit is set to true.

7.9 Pinning a page in memormy is done by an application requesting that page, this
increases the buffer manager's pin count for that page. Unpinning a page in memory is
done by an application telling the buffer manager that its done using that page, this
decreases the buffer manager's pin count for that page.

7.10 When a page is modified, its by a program seperate from the buffer manager. This
program must tell the buffer manager that it has modified the page, when this happens
the buffer manager sets the dirty bit for that frame from false to true. Since the BM
will write any dirty pages to disk upon replacement, we're sure our changes will get 
propagated to disk.

7.11 When there is a page request and all the pages are dirty, then one frame is 
selected by the page replacement policy, it is written to disk, and the requested page
is read into the selected frame.

7.12 Sequential flodding of the buffer pool is a problem related to using the 
least recently used page replacement algorithm. The problem occurs when a file 
is being read sequentially and the pages being read are pages that have just been swapped
out, the problem that occurs here is that the page that is being swapped out is the 
most likely to be used again soon.

7.13