From 19155d781a646836d5142a605b9bebcdea307076 Mon Sep 17 00:00:00 2001 From: Balajinaidu V <72434180+ba1ajinaidu@users.noreply.github.com> Date: Fri, 27 Oct 2023 12:43:12 +0530 Subject: [PATCH] Fix some minor changes (#3) Co-authored-by: ba1ajinaidu --- config.toml | 2 +- content/posts/k8s-and-postgres.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/config.toml b/config.toml index fc3a653..0541125 100644 --- a/config.toml +++ b/config.toml @@ -45,7 +45,7 @@ enableEmoji = true avatar = "kool_flork.jpeg" intro = "ba1ajinaidu" name = "Balajinaidu V" - description = "Complete Technical Works" + description = "Nerding out online" [[params.socialIcons]] name = "github" diff --git a/content/posts/k8s-and-postgres.md b/content/posts/k8s-and-postgres.md index b65adfa..ad5e74d 100644 --- a/content/posts/k8s-and-postgres.md +++ b/content/posts/k8s-and-postgres.md @@ -175,7 +175,7 @@ So, is it safe to run Postgres databases on a Kubernetes cluster? If you are running 1 Postgres database on a cluster, you can schedule the Postgres pods on particular nodes using taints and tolerations where you have enabled hugepages, and it can use all the hugepages of the underlying node. But if you want to run multiple databases on a cluster, then Postgres won't play nice with k8s; it's not very reliable, and you might face these issues. And obviously, you can always go back and disable hugepages and run multiple databases on a cluster; you'll lose all the performance advantages provided by hugepages, and the OOM Killer can crash the Postgres processes, as explained in the article by Percona. - +I'm not a expert, if someone has a solution/work around for this issue, please let me know :) ### References 1. [More about page tables in linux](https://lwn.net/Articles/717293/)