Linux has kind of two forms of memory pages (entries in RAM), one is a file cache (page cache) and the other is "memory allocated by programs for work" (anonymous pages).
When you look at memory consumed by a process you are looking at RSS, page/file cache is part of kernel and for example in btop corresponds to Cached.
Page cache can never be moved into swap - that would be the same as duplicating the file from one place on a disk to another place on a (possibly different) disk.If more memory is needed, page cache is evicted (written back into the respective file, if changed).
Only anonymous pages (not backed by anything permanent) can be moved into swap.
So what does "PostgreSQL heavily relies on the OSs disk cache" mean?
The more free memory there is, the more files can be kept cached in RAM and the faster postgres can then retrieve these files.
When you add zram, you dedicate part of actual RAM to a compressed swap device which, as I said above, will never contain page cache.In theory this still increases the total available memory but in reality that is only true if you configure the kernel to aggressively "swap" anonymous pages into the zram backed swap.
Notes: I tried to simplify this a bit so it might not be exact, also if you look at a process, the memory consumed by it is called RSS and it contains multiple different things not just memory directly allocated by the code of the program.
Had to solve the same problem few months ago, user provided content and so, user provided translations.We use postgres everywhere and we had to support 3 languages initially with one more eventually, so we decied to use json fields for anything that could be translated (which wasn't too much).
Mind you, this was basically a (temporarily permanent) prototype project but (fresh) postgres has a good support and operators for json so it worked alright.
EDIT: I remembered that hstore might be a good alternative too, I think it was slightly less "heavy" and had better operators for the kind of access we needed
it's good, the bad: beta maps are small so it's not exactly the BF experience of old, there should be bigger maps on release. Also no server browser, invasive antichet and EA, but it is good
Unsure how well known it is, but flameshot (screenshot tool).
I prefer CLI usually, so:
zoxide, the zsh git plugin for aliases (e.g.: gst is git status), fzf zsh plugin and the tldr command comes in handy sometimes.
Also, this might be useful just for me, but due to orientation of my living space, I have to fiddle with monitor brightness at least three times a day so I made myself a little Qt tray wrapper around ddcutil's ddcquery which can change standard vesa monitors brightness/contrast (DDC/CI communication).There is also ddcui/gddccontrol GUI that does the same thing.
before getting a pocketbook I was using ReadEra and it worked alright (for basic reading)