| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeremy Palmer <JPalmer(at)linz(dot)govt(dot)nz> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Subject: | Re: Win32 Backend Cash - pre-existing shared memory block is still in use |
| Date: | 2010-08-19 13:42:21 |
| Message-ID: | 26389.1282225341@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Jeremy Palmer <JPalmer(at)linz(dot)govt(dot)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.
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2010-08-19 13:46:17 | Re: Win32 Backend Cash - pre-existing shared memory block is still in use |
| Previous Message | Sam Mason | 2010-08-19 12:41:57 | Re: Massively Parallel transactioning? |