Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 1049C63266D for ; Wed, 2 Jun 2010 07:58:59 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 20376-01 for ; Wed, 2 Jun 2010 10:58:51 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ww0-f46.google.com (mail-ww0-f46.google.com [74.125.82.46]) by mail.postgresql.org (Postfix) with ESMTP id 3EBD7632726 for ; Wed, 2 Jun 2010 07:58:51 -0300 (ADT) Received: by wwb28 with SMTP id 28so2765746wwb.19 for ; Wed, 02 Jun 2010 03:58:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=LBTXgIaO5krks5fBqK16ZfwCCZeD+l3qe8vsOX76RS4=; b=DBBngfUvDnld7uMeZG28zV1ib3Tlc/IDe3Edc4/svE+RAw1l7baiw5mAokAldHzU5T IQv+WI1QZ8j6ZY/+cHcHR9jrD7yEWO5ABw93Mn6kWJFawHPfDh/6jWgU3vEUpco/IuEQ o3Z8qkrsDgsvz/WT9FK5w49m7R4+wxSy/atOY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=hm5WfM+ZgPQd40OTLycRTi9ln/EzI7V5DaOABnPO433VHkVR5mNqdFbEnUq39q7c7g AeAFFht5YoNhPBIbuI0xZS5/Fl6Cw2wJRdh+Wd9IhJGFUZCeqZF0yhVRPEBN5QubaCOb 4QGifCsd1lUGVZgdH1rOj6d9snL7FpfEmc09s= Received: by 10.227.138.18 with SMTP id y18mr7420595wbt.198.1275476328808; Wed, 02 Jun 2010 03:58:48 -0700 (PDT) Received: from rachelcc-lap.cse.org.uk (fpc1-hawk1-0-0-cust7.aztw.static.cable.virginmedia.com [82.33.204.200]) by mx.google.com with ESMTPS id l23sm58072038wbb.8.2010.06.02.03.58.48 (version=SSLv3 cipher=RC4-MD5); Wed, 02 Jun 2010 03:58:48 -0700 (PDT) Message-ID: <4C063967.4070705@gmail.com> Date: Wed, 02 Jun 2010 11:58:47 +0100 From: Tom Wilcox User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: requested shared memory size overflows size_t Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201006/36 X-Sequence-Number: 38892 Hi, Sorry to revive an old thread but I have had this error whilst trying to configure my 32-bit build of postgres to run on a 64-bit Windows Server 2008 machine with 96GB of RAM (that I would very much like to use with postgres). I am getting: 2010-06-02 11:34:09 BSTFATAL: requested shared memory size overflows size_t 2010-06-02 11:41:01 BSTFATAL: could not create shared memory segment: 8 2010-06-02 11:41:01 BSTDETAIL: Failed system call was MapViewOfFileEx. which makes a lot of sense since I was setting shared_buffers (and effective_cache_size) to values like 60GB.. Is it possible to get postgres to make use of the available 96GB RAM on a Windows 32-bit build? Otherwise, how can I get it to work? Im guessing my options are: - Use the 64-bit Linux build (Not a viable option for me - unless from a VM - in which case recommendations?) or - Configure Windows and postgres properly (Preferred option - but I don't know what needs to be done here or if Im testing properly using Resource Monitor) Thanks, Tom