Postgres Pro
Downloads
Home   >   mailing lists

Re: Win32 Backend Cash - pre-existing shared memory block is still in use - Mailing list pgsql-general

From Scott Marlowe
Subject Re: Win32 Backend Cash - pre-existing shared memory block is still in use
Date
Msg-id AANLkTinoBPesQtX=4bc3sJ8Ng5MGS4kiudd0MQ8BNcb_@mail.gmail.com
Whole thread Raw
In response to Re: Win32 Backend Cash - pre-existing shared memory block is still in use  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Win32 Backend Cash - pre-existing shared memory block is still in use
List pgsql-general
Tree view 
On Tue, Aug 24, 2010 at 11:23 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Scott Marlowe <scott.marlowe@gmail.com> writes:
>> 512M is still REALLY high for a 32 bit postgresql.  Have you tried
>> something in the 16Meg range?
>
> Cutting his value for shared_buffers (currently about 800MB) might be
> wise too.  I'm not sure what the effectively available address space
> for a win32 process is, but if there's any inefficiency in the way
> the address space is laid out, those numbers could be enough to be
> trouble.

I believe it's limited to 3Gigs.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Win32 Backend Cash - pre-existing shared memory block is still in use
Next
From: Jeremy Palmer
Date:
Subject: Re: Win32 Backend Cash - pre-existing shared memory block is still in use