From: | Tom Wilcox <hungrytom(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: requested shared memory size overflows size_t |
Date: | 2010-06-14 23:21:35 |
Message-ID: | 4C16B97F.4080201@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Thanks. I will try with a more sensible value of wal_buffers.. I was
hoping to keep more in memory and therefore reduce the frequency of disk
IOs..
Any suggestions for good monitoring software for linux?
On 15/06/2010 00:08, Robert Haas wrote:
> On Mon, Jun 14, 2010 at 2:53 PM, Tom Wilcox<hungrytom(at)gmail(dot)com> wrote:
>
>> maintenance_work_mem=4GB
>> work_mem=4GB
>> shared_buffers=4GB
>> effective_cache_size=4GB
>> wal_buffers=1GB
>>
> It's pretty easy to drive your system into swap with such a large
> value for work_mem - you'd better monitor that carefully.
>
> The default value for wal_buffers is 64kB. I can't imagine why you'd
> need to increase that by four orders of magnitude. I'm not sure
> whether it will cause you a problem or not, but you're allocating
> quite a lot of shared memory that way that you might not really need.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Crooke | 2010-06-15 00:26:51 | Re: requested shared memory size overflows size_t |
Previous Message | Lacey Powers | 2010-06-14 23:15:37 | Re: Re: Command Prompt 8.4.4 PRMs compiled with debug/assert enabled |