| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | problem with memory |
| Date: | 2009-05-26 15:32:46 |
| Message-ID: | 162867790905260832j29b1fd2fqfdeb2cb954e77d01@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello
one czech PostgreSQL user reports problem with memory - probable memleak?
Is possible to diagnose some from log?
Postgres ver. 8.3.7 .
Server 8G RAM, 32b Debian Etch.
Configuration:
shared_buffers = 324000 # min 16 or max_connections*2, 8KB each
temp_buffers = 16000 # min 100, 8KB each
work_mem = 8126 # min 64, size in KB
maintenance_work_mem = 16384 # min 1024, size in KB
max_stack_depth = 7680 # min 100, size in KB
max_fsm_pages = 200000 # min max_fsm_relations*16, 6 bytes
max_fsm_relations = 12000 # min 100, ~70 bytes each
effective_cache_size = 300000 # typically 8KB each
http://jyxo.cz/misc/sql.error.txt
Thank you
Pavel Stehule
| From | Date | Subject | |
|---|---|---|---|
| Next Message | tomas | 2009-05-26 15:33:46 | Re: generic options for explain |
| Previous Message | Dimitri Fontaine | 2009-05-26 15:26:05 | Re: generic options for explain |