Heikki Linnakangas wrote:
The way you update the DSM is quite interesting. When a page is dirtied, the BM_DSM_DIRTY flag is set in the buffer descriptor. The corresponding bit in the DSM is set lazily in FlushBuffer whenever BM_DSM_DIRTY is set. That's a clever way to avoid contention on updates. But does it work for tables that have a small hot part that's updated very frequently?
I think there is no problem. Bloating will make pages including the unnecessary area which will not be accessed. Soon, those pages will be registered into DSM.
Or, though it expands however, do you assume accessing all pages equally? -- Hiroki Kataoka <[EMAIL PROTECTED]> ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
