From: Tom Wilcox <hungrytom@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: requested shared memory size overflows size_t
Date: Tue, 15 Jun 2010 00:21:35 +0100
Message-ID: <4C16B97F.4080201@gmail.com> (raw)
In-Reply-To: <AANLkTinl1XU1IYUv2lmBXeKPKk37TKutBSNbcGvPmjJI@mail.gmail.com>
References: <584872.74177.qm@web39702.mail.mud.yahoo.com>
<4C167A8D.1060002@gmail.com>
<AANLkTinl1XU1IYUv2lmBXeKPKk37TKutBSNbcGvPmjJI@mail.gmail.com>
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@gmail.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.
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: hungrytom@gmail.com, robertmhaas@gmail.com
Subject: Re: requested shared memory size overflows size_t
In-Reply-To: <4C16B97F.4080201@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox