| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: problem with memory |
| Date: | 2009-05-26 16:00:02 |
| Message-ID: | 13165.1243353602@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> one czech PostgreSQL user reports problem with memory - probable memleak?
> Is possible to diagnose some from log?
If he's getting an actual "out of memory" error, let's see the memory
context map that gets dumped to the server log (or more specifically,
to stderr).
> Server 8G RAM, 32b Debian Etch.
> shared_buffers = 324000 # min 16 or max_connections*2, 8KB each
Although you may have told us enough right here. 2.5GB of shared
buffers in a 4GB address space (with probably only 3GB available to the
application) isn't a very sane choice. Back that off or run 64-bit.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-05-26 16:18:17 | Re: PostgreSQL Developer meeting minutes up |
| Previous Message | Andrew Dunstan | 2009-05-26 15:59:17 | Re: PostgreSQL Developer meeting minutes up |