Databases are special. They ofte implement their own optimizations, faster than more general system optimizations.
For examole: https://www.postgresql.org/docs/current/wal-intro.html
Because WAL restores database file contents after a crash, journaled file systems are not necessary for reliable storage of the data files or WAL files. In fact, journaling overhead can reduce performance, especially if journaling causes file system data to be flushed to disk. Fortunately, data flushing during journaling can often be disabled with a file system mount option, e.g., data=writeback on a Linux ext3 file system. Journaled file systems do improve boot speed after a crash.
I didn’t see much in the docs about swap, but I wouldn’t be suprised if postgres also had memory optimizations, like it included it’s own form of in memory compression.
Your best bet is probably to ask someone who is familiar with the internals of postgres.
Okay. This sounds very strange, but I had a similar issue with the nintendo switch pro controller and binding of isaac. I played around with antimicrox, but the real solution I found was to launch steam and leave it running. Then, my pro controller would magically work.
I didn’t have to launch the game via steam either, which is what made it even stranger to me.