Postgres Pro
Downloads
Home   >   mailing lists

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

From Magnus Hagander
Subject Re: Win32 Backend Cash - pre-existing shared memory block is still in use
Date
Msg-id AANLkTini8WSviPm4ybGZh1JAcO=OBQQd2QhChWCmSPcS@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 Thu, Aug 19, 2010 at 15:42, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Jeremy Palmer <JPalmer@linz.govt.nz> writes:
>> Could it be that I have too much memory allocated for postgresql? My resource settings are:
>> shared_buffers = 94952
>> temp_buffers = 1GB
>> work_mem = 19339
>> maintenance_work_mem = 191845
>> max_stack_depth = 2MB
>
> 1GB for temp_buffers is a *LOT*.  You do realize that's per backend?
> Those other settings don't look too unreasonable.

Definitely - particularly since this is a 32-bit version, that's
getting very close to the address space limits...

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

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: Gordon
Date:
Subject: Extract created and last modified data