Dangerous hint in the PostgreSQL manual

From: Listaccount <lst_hoe01(at)kwsoft(dot)de>
To: pgsql-admin(at)postgresql(dot)org
Subject: Dangerous hint in the PostgreSQL manual
Date: 2007-12-10 15:26:12
Message-ID: 20071210162612.a9y113hzjkookooc@webmail.kwsoft.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-docs

Hello

I have been trapped by the advice from the manual to use "sysctl -w
vm.overcommit_memory=2" when using Linux (see 16.4.3. Linux Memory
Overcommit). This value should only be used when PostgreSQL is the
only Application running on the machine in question. It should be
checked against the values "CommitLimit" and "Committed_AS" in
/proc/meminfo on a longer running system. If "Committed_AS" reaches or
come close to "CommitLimit" one should not set overcommit_memory=2 (see
http://www.redhat.com/archives/rhl-devel-list/2005-February/msg00738.html). I
think it should be included in the manual as a warning because with
this setting the machine in question may get trouble with "fork
failed" even if the standard system tools report a lot of free memory
causing confusion to the admins.

Regards

Andreas

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Joshua D. Drake 2007-12-10 16:53:29 Re: [ADMIN] Dangerous hint in the PostgreSQL manual
Previous Message Scott Marlowe 2007-12-07 20:36:39 Re: pg_dump question

Browse pgsql-docs by date

  From Date Subject
Next Message Joshua D. Drake 2007-12-10 16:53:29 Re: [ADMIN] Dangerous hint in the PostgreSQL manual
Previous Message Bruce Momjian 2007-12-10 14:51:17 Re: [GENERAL] full_page_writes = off?