Re: concurrent Postgres on NUMA - howto ?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Mauricio Breternitz" <mbjsql(at)hotmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: concurrent Postgres on NUMA - howto ?
Date: 2001-04-23 23:43:05
Message-ID: 24147.988069385@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Mauricio Breternitz" <mbjsql(at)hotmail(dot)com> 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 the LockBuffer calls are, not where
WriteBuffer is called.

I really question whether you want to do anything like this at all.
Seems like accessing the shared buffers right where they are will be
fastest; your approach will entail a huge amount of extra data copying.
Considering that a backend doesn't normally touch every byte on a page
that it accesses, I wouldn't be surprised if full-page copying would
net out to being more shared-memory traffic, rather than less.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-04-23 23:51:38 Re: refusing connections based on load ...
Previous Message Len Morgan 2001-04-23 22:20:36 Re: refusing connections based on load ...