pgsql: Document how to prevent PostgreSQL itself from exhausting memory

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Document how to prevent PostgreSQL itself from exhausting memory
Date: 2012-08-30 18:25:31
Message-ID: E1T79Qp-0006Wl-SQ@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
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
------
REL9_1_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/f6956eb74edcdf21339f9d200ef63c4015a5f4cb

Modified Files
--------------
doc/src/sgml/runtime.sgml | 20 +++++++++++++++++---
1 files changed, 17 insertions(+), 3 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2012-08-30 18:33:20 pgsql: Suppress creation of backwardly-indexed paths for LATERAL join c
Previous Message Bruce Momjian 2012-08-30 18:08:21 Re: pgsql: Add missing period to detail message.