From: | Dan Eloff <dan(dot)eloff(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | File IO - why does PG do things in pages? |
Date: | 2009-11-26 21:14:58 |
Message-ID: | 4817b6fc0911261314m37c8e56eh5678f81105847af9@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Hackers,
I've familiarized myself a little with the architecture of postgresql,
largely because it's interesting. There's one thing I can't quite
figure out though, and it seems that there's no better group of people
in the world to ask about it.
At the lower levels in PG, reading from the disk into cache, and
writing from the cache to the disk is always done in pages.
Why does PG work this way? Is it any slower to write whole pages
rather than just the region of the page that changed? Conversely, is
it faster? From what I think I know of operating systems, reading
should bring the whole page into the os buffers anyway, so reading the
whole page instead of just part of it isn't much more expensive.
Perhaps writing works similarly?
Thanks,
-Dan
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-11-26 21:15:51 | Re: Documentation broken due to typo |
Previous Message | Jeff Davis | 2009-11-26 20:28:19 | Documentation broken due to typo |