Re: [PATCHES] How can I use 2GB of shared buffers on Windows?

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Takayuki Tsunakawa <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCHES] How can I use 2GB of shared buffers on Windows?
Date: 2007-02-09 14:32:10
Message-ID: 20070209143210.GB20293@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Fri, Feb 09, 2007 at 07:31:33PM +0900, Takayuki Tsunakawa wrote:
> 1. PostgreSQL tries to read data from disk into database cache.
> 2. The kernel tries to allocate filesystem buffers by paging out
> PostgreSQL's memory (possibly shared buffers).
> 3. PostgreSQL finds data requested by its clients in database cache,
> and tries to get it in memory.
> 4. But the shared buffers are paged out, and page-ins happen.

One of the biggest issues with large shared memory segments is that we
can't be sure they'll actually stay in memory. So your shared memory
block should not be too much larger than your working set.

So yes, if you make a really large segment, the problem you describe
may happen.

Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-02-09 14:49:25 Re: [PATCHES] How can I use 2GB of shared buffers on Windows?
Previous Message Andrew Dunstan 2007-02-09 14:30:23 Re: pgsql: Add lock matrix to documentation.

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2007-02-09 14:40:37 Re: Feature: POSIX Shared memory support, round 2
Previous Message Tom Lane 2007-02-09 14:28:28 Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch