I am learning the data format of DBMS and found we have a term: page.
Pages are the fetched data in main memory from external storage (eg. a disk, SSD) and several pages would be "cached" firstly to the Low Level Cache, when these pages are acquired by a query.
That reminds me of the same term page used in operating systems and computer architecture. Some formal descriptions about this "paging" from Wiki are:
Paging is a memory management scheme by which a computer stores and retrieves data from secondary storage for use in main memory. In this scheme, the operating system retrieves data from secondary storage in same-size blocks called pages. Paging is an important part of virtual memory implementations in modern operating systems, using secondary storage to let programs exceed the size of available physical memory.
So it comes to the first question:
Does the term page carry the same meaning in DBMS and in OS?
- If yes, can you explain question 2 a little bit?
- If not, can you explain why? Do they have different way to be implemented?
A step more:
- In the lecture we learn the N-ary Storage Model (NSM or slotted pages) and PAX (Partition Attributes Across) refer to this paper from Prof. Ailamaki. Assume page has the same meaning in DBMS and OS, why do we specify the NSM and PAX only in DBMS? Can this page format be portable to OS? (About the paper will be helpful, that you just go quicklythrough the data layout and the figures.)
The question 2 is the main reason, that I raise question here and start to ask myself, why NSM, PAX pages are special for DBMS. This question is more general and not focused on any particular DBMS in mind.