Search Postgresql Archives

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jeremy Palmer <JPalmer@xxxxxxxxxxxx> 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.

I looked into the code and noticed that temp buffers are allocated
directly in TopMemoryContext, so this setting doubtless explains
the large amount of stuff in TopMemoryContext in your memory map.
I'm thinking we should push those buffers into a context of their own,
just so that it's clearer from the map where the memory went.

			regards, tom lane

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux