Skip to content

Commit

Permalink
Fix some minor changes (#3)
Browse files Browse the repository at this point in the history
Co-authored-by: ba1ajinaidu <[email protected]>
  • Loading branch information
ba1ajinaidu and ba1ajinaidu authored Oct 27, 2023
1 parent 95357f9 commit 19155d7
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion config.toml
Original file line number Diff line number Diff line change
Expand Up @@ -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"
Expand Down
2 changes: 1 addition & 1 deletion content/posts/k8s-and-postgres.md
Original file line number Diff line number Diff line change
Expand Up @@ -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/)
Expand Down

0 comments on commit 19155d7

Please sign in to comment.