Skip site navigation (1) Skip section navigation (2)

pgsql: Document how to prevent PostgreSQL itself from exhaustingmemory

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Document how to prevent PostgreSQL itself from exhaustingmemory
Date: 2012-08-30 18:25:31
Message-ID: E1T79Qp-0006Wf-Ow@gemulon.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Document how to prevent PostgreSQL itself from exhausting memory.

The existing documentation in Linux Memory Overcommit seemed to
assume that PostgreSQL itself could never be the problem, or at
least it didn't tell you what to do about it.

Per discussion with Craig Ringer and Kevin Grittner.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/35738b5906bb80bc4bb77ce1adea7dfbd3f64274

Modified Files
--------------
doc/src/sgml/runtime.sgml |   18 ++++++++++++++++--
1 files changed, 16 insertions(+), 2 deletions(-)

pgsql-committers by date

Next:From: Tom LaneDate: 2012-08-30 18:33:20
Subject: pgsql: Suppress creation of backwardly-indexed paths for LATERAL joinc
Previous:From: Bruce MomjianDate: 2012-08-30 18:08:21
Subject: Re: pgsql: Add missing period to detail message.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group