From: | Valentine Gogichashvili <valgog(at)gmail(dot)com> |
---|---|
To: | Lampa <lampacz(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #6186: out of memory while analyze |
Date: | 2011-09-01 09:48:18 |
Message-ID: | CAP93muV9PTiRFr7gqDTDwFRiS_TJMUb2iq2hS80GgRi7a05CWw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
>
>
> ssl = false
> shared_buffers = 900MB # min 128kB
> work_mem = 100MB # min 64kB
> maintenance_work_mem = 524MB # min 1MB
> fsync = off # turns forced synchronization on
> or off
> synchronous_commit = off # immediate fsync at commit
> full_page_writes = off # recover from partial page writes
> effective_cache_size = 1GB
> default_statistics_target = 8000 # range 1-10000
>
>
> Also tried change maintenance_work_mem to 2G and same result.
> Imposible to set over 2GB (FATAL: 3145728 is outside the valid range
> for parameter "maintenance_work_mem" (1024 .. 2097151))
>
>
Actually, it also can be, that your commit limit is reached. Can you also
look in the /proc/meminfo -> CommitLimit and Commit_AS. These values should
not be too close to each other.
What are the values
for /proc/sys/vm/swappiness, /proc/sys/vm/overcommit_memory
and /proc/sys/vm/overcommit_ratio? What is your swap size. They all
influence CommitLimit and the amount of memory, you can get.
-- Valentin
From | Date | Subject | |
---|---|---|---|
Next Message | Lampa | 2011-09-01 09:59:02 | Re: BUG #6186: out of memory while analyze |
Previous Message | Incorrect result from operator overlaps | 2011-09-01 08:27:27 | BUG #6192: Incorrect result from operator "overlaps" |