diff options
| author | Bruce Momjian <bruce@momjian.us> | 2014-10-13 17:23:36 -0400 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2014-10-13 17:23:36 -0400 |
| commit | ebd33f27ab023ef0e72ba162f2974ec49d96e8e3 (patch) | |
| tree | 98d08bfbe21dffbc1e28c6c718ea4433a51ef39b | |
| parent | fe65280fea7e3c930727ed74328613a4410e487a (diff) | |
| download | postgresql-ebd33f27ab023ef0e72ba162f2974ec49d96e8e3.tar.gz postgresql-ebd33f27ab023ef0e72ba162f2974ec49d96e8e3.zip | |
doc: mention more changes needed to use huge pages
Report by Laurence Parry
| -rw-r--r-- | doc/src/sgml/runtime.sgml | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index 639b288e062..026850a1cf5 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1361,6 +1361,13 @@ $ <userinput>sysctl -w vm.nr_hugepages=3170</userinput> </para> <para> + It is also necessary to give the database server operating system + user permission to use huge pages by setting + <varname>vm.hugetlb_shm_group</> via <application>sysctl</>, and + permission to lock memory with <command>ulimit -l</>. + </para> + + <para> The default behavior for huge pages in <productname>PostgreSQL</productname> is to use them when possible and to fallback to normal pages when failing. To enforce the use of huge |