aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistutil.c
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2012-08-30 14:14:22 -0400
committerRobert Haas <rhaas@postgresql.org>2012-08-30 14:23:05 -0400
commitf6956eb74edcdf21339f9d200ef63c4015a5f4cb (patch)
tree319d7b90ff6749e3e5bf87f8b8b9b5bc82c9e0c4 /src/backend/access/gist/gistutil.c
parent657face6fea6e8e29944b839c4e5ceb6c63e251e (diff)
downloadpostgresql-f6956eb74edcdf21339f9d200ef63c4015a5f4cb.tar.gz
postgresql-f6956eb74edcdf21339f9d200ef63c4015a5f4cb.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/gistutil.c')
0 files changed, 0 insertions, 0 deletions