Re: Win32 Backend Cash - pre-existing shared memory block is still in use

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

I'm running on a server with 3.7GB of RAM.

I will adjust the logging level and wait for another crash. Should I set the level to 'debug5'? The cluster is for development purposes, so I don't mind the overhead.

Cheers,
Jeremy

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Thursday, August 19, 2010 4:07 AM
To: Alvaro Herrera
Cc: Jeremy Palmer; pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Win32 Backend Cash - pre-existing shared memory block is still in use

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> This is a memory dump and could be unrelated (or maybe not).

>> TopMemoryContext: 268428304 total in 26 blocks; 5528 free (22 chunks); 268422776 used

That's an unreasonably large amount of stuff in TopMemoryContext :-(.
I wonder what caused that? It's not clear that'd have led to the crash
though.

regards, tom lane
______________________________________________________________________________________________________

This message contains information, which is confidential and may be subject to legal privilege.
If you are not the intended recipient, you must not peruse, use, disseminate, distribute or copy this message.
If you have received this message in error, please notify us immediately (Phone 0800 665 463 or info(at)linz(dot)govt(dot)nz) and destroy the original message.
LINZ accepts no responsibility for changes to this email, or for any attachments, after its transmission from LINZ.

Thank you.
______________________________________________________________________________________________________