From f1795463bf503a6fca909d77f598f641f9349f56 Mon Sep 17 00:00:00 2001
From: Shay <hillerys@element.io>
Date: Tue, 30 Nov 2021 19:05:20 -0800
Subject: [PATCH] Add a note about huge pages to our Postgres doc (#11467)

* Add note to postgres doc about hugepages

* Newsfragment
---
 changelog.d/11467.misc | 1 +
 docs/postgres.md       | 3 +++
 2 files changed, 4 insertions(+)
 create mode 100644 changelog.d/11467.misc

diff --git a/changelog.d/11467.misc b/changelog.d/11467.misc
new file mode 100644
index 000000000000..84e8a5ab4e00
--- /dev/null
+++ b/changelog.d/11467.misc
@@ -0,0 +1 @@
+Add a note about postgres memory management and hugepages to postgres doc.
\ No newline at end of file
diff --git a/docs/postgres.md b/docs/postgres.md
index 083b0aaff01f..e4861c1f127f 100644
--- a/docs/postgres.md
+++ b/docs/postgres.md
@@ -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
+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