DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=RUzsXtH9LUVugdHXKu6mskbFzaPrvmjNQ0gxl/xxJKf0QGZMHIJhKbtFraCa7Lybu3IieXX2ruMd0DoTh2UBdVYB8nUBnMn4sq3mvG7WLXjAKakSq6xfUADN9A6Hip4+LjmTA2isJ/IrrrezXktKq+ntYh0cTMrKUqYcva1Hkt0=;
Message-ID: <689977.86245.qm@web39708.mail.mud.yahoo.com>
Date: Wed, 2 Jun 2010 18:26:56 -0700 (PDT)
From: Bob Lunney <bob_lunney@yahoo.com>
Subject: Re: requested shared memory size overflows size_t
To: pgsql-performance@postgresql.org, Tom Wilcox <hungrytom@googlemail.com>
In-Reply-To: <4C063967.4070705@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Tom,=0A=0AA 32 bit build could only reference at most 4 Gb - certainly not =
60 Gb.  Also, Windows doesn't do well with large shared buffer sizes anyway=
.  Try setting shared_buffers to 2 Gb and let the OS file system cache hand=
le the rest.=0A=0AYour other option, of course, is a nice 64-bit linux vari=
ant, which won't have this problem at all.=0A=0AGood luck!=0A=0ABob Lunney=
=0A=0A--- On Wed, 6/2/10, Tom Wilcox <hungrytom@googlemail.com> wrote:=0A=
=0A> From: Tom Wilcox <hungrytom@googlemail.com>=0A> Subject: Re: [PERFORM]=
 requested shared memory size overflows size_t=0A> To: pgsql-performance@po=
stgresql.org=0A> Date: Wednesday, June 2, 2010, 6:58 AM=0A> Hi,=0A> =0A> So=
rry to revive an old thread but I have had this error=0A> whilst trying to =
configure my 32-bit build of postgres to=0A> run on a 64-bit Windows Server=
 2008 machine with 96GB of RAM=0A> (that I would very much like to use with=
 postgres).=0A> =0A> I am getting:=0A> =0A> 2010-06-02 11:34:09 BSTFATAL:=
=A0 requested shared memory=0A> size overflows size_t=0A> 2010-06-02 11:41:=
01 BSTFATAL:=A0 could not create shared=0A> memory segment: 8=0A> 2010-06-0=
2 11:41:01 BSTDETAIL:=A0 Failed system call was=0A> MapViewOfFileEx.=0A> =
=0A> which makes a lot of sense since I was setting=0A> shared_buffers (and=
 effective_cache_size) to values like=0A> 60GB..=0A> =0A> Is it possible to=
 get postgres to make use of the available=0A> 96GB RAM on a Windows 32-bit=
 build? Otherwise, how can I get=0A> it to work?=0A> =0A> Im guessing my op=
tions are:=0A> =0A> - Use the 64-bit Linux build (Not a viable option for m=
e -=0A> unless from a VM - in which case recommendations?)=0A> or=0A> - Con=
figure Windows and postgres properly (Preferred option=0A> - but I don't kn=
ow what needs to be done here or if Im=0A> testing properly using Resource =
Monitor)=0A> =0A> Thanks,=0A> Tom=0A> =0A> =0A> -- Sent via pgsql-performan=
ce mailing list (pgsql-performance@postgresql.org)=0A> To make changes to y=
our subscription:=0A> http://www.postgresql.org/mailpref/pgsql-performance=
=0A> =0A=0A=0A