Mauricio Breternitz [EMAIL PROTECTED] writes:
Notice that WriteBuffer would just put the fresh copy of the page
out in the shared space.
Other backends would get the latest copy of the page when
THEY execute BufferAlloc() afterwards.
You seem to be assuming that BufferAlloc is
]
CC: [EMAIL PROTECTED]
Subject: Re: [HACKERS] concurrent Postgres on NUMA - howto ?
Date: Mon, 23 Apr 2001 19:43:05 -0400
Mauricio Breternitz [EMAIL PROTECTED] writes:
My concern is whether that is enough to maintain consistency
in the buffer cache
No, it isn't --- for one thing
Folks:
I'm planning a port of Postgres to a multiprocessor
architecture in which all nodes have both local memory
and fast access to a shared memory. Shared memory it more
expensive than local memory.
My intent is to put the shmem lock structures in
shared memory, but use a
Mauricio Breternitz [EMAIL PROTECTED] writes:
My concern is whether that is enough to maintain consistency
in the buffer cache
No, it isn't --- for one thing, WriteBuffer wouldn't cause other
backends to update their copies of the page. At the very least you'd
need to synchronize where
