| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Wilcox <hungrytom(at)gmail(dot)com> |
| Cc: | Bob Lunney <bob_lunney(at)yahoo(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: requested shared memory size overflows size_t |
| Date: | 2010-06-14 23:08:14 |
| Message-ID: | AANLkTinl1XU1IYUv2lmBXeKPKk37TKutBSNbcGvPmjJI@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lacey Powers | 2010-06-14 23:14:47 | Re: Re: Command Prompt 8.4.4 PRMs compiled with debug/assert enabled |
| Previous Message | Andrew Dunstan | 2010-06-14 22:53:29 | Re: Re: Command Prompt 8.4.4 PRMs compiled with debug/assert enabled |