Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Add a note about huge pages to our Postgres doc #11467

Merged
merged 2 commits into from
Dec 1, 2021
Merged

Add a note about huge pages to our Postgres doc #11467

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5f70853
Add note to postgres doc about hugepages
H-Shay Nov 30, 2021
1d92630
Newsfragment
H-Shay Nov 30, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions changelog.d/11467.misc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Add a note about postgres memory management and hugepages to postgres doc.
3 changes: 3 additions & 0 deletions docs/postgres.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,6 +118,9 @@ performance:
Note that the appropriate values for those fields depend on the amount
of free memory the database host has available.

Additionally, admins of large deployments might want to consider using huge pages
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"huge pages" is a linux kernel feature, so this only applies to deployments running on Linux. Maybe it's worth saying "large deployments on Linux".

(We don't really support running it on anything else AFAIK, so maybe this is a needless distinction to draw. I leave it to your discretion!)

to help manage memory, especially when using large values of `shared_buffers`. You
can read more about that [here](https://www.postgresql.org/docs/10/kernel-resources.html#LINUX-HUGE-PAGES).

## Porting from SQLite

Expand Down