Re: oom_killer - Mailing list pgsql-performance

From Claudio Freire
Subject Re: oom_killer
Date
Msg-id BANLkTi=d3aJ20GnRGO_3JXyju0mcqe65HA@mail.gmail.com
Whole thread Raw
In response to Re: oom_killer  (Tory M Blue <tmblue@gmail.com>)
Responses Re: oom_killer  (Tory M Blue <tmblue@gmail.com>)
List pgsql-performance
On Thu, Apr 21, 2011 at 5:50 PM, Tory M Blue <tmblue@gmail.com> wrote:
> # - Checkpoints -
> checkpoint_segments = 100
> max_connections = 300
> shared_buffers = 2500MB       # min 128kB or max_connections*16kB
> max_prepared_transactions = 0
> work_mem = 100MB
> maintenance_work_mem = 128MB
> fsync = on

That's an unrealistic setting for a 32-bit system, which can only
address 3GB of memory per process.

You take away 2500MB for shared buffers, that leaves you only 500M for
data, some of which is code.

There's no way PG can operate with 100MB work_mem llike that.

Either decrease shared_buffers, or get a 64-bit system.

pgsql-performance by date:

Previous
From: Tory M Blue
Date:
Subject: Re: oom_killer
Next
From: Tory M Blue
Date:
Subject: Re: oom_killer