diff options
| author | Robert Haas <rhaas@postgresql.org> | 2012-08-30 14:14:22 -0400 |
|---|---|---|
| committer | Robert Haas <rhaas@postgresql.org> | 2012-08-30 14:24:07 -0400 |
| commit | 35738b5906bb80bc4bb77ce1adea7dfbd3f64274 (patch) | |
| tree | e15388a27a59c7c53ba947b11e671bc3c0566503 /src/backend/access/gist | |
| parent | 3e6eb0dd0a0982c61420a0d18d3e485bd2c2819c (diff) | |
| download | postgresql-35738b5906bb80bc4bb77ce1adea7dfbd3f64274.tar.gz postgresql-35738b5906bb80bc4bb77ce1adea7dfbd3f64274.zip | |
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.
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions