3 ms·
> Previously Mess With DNS was using a Postgres database. This was problematic because I only gave the Postgres machine 256MB of RAM, which meant that the datab
by e12e 2y ago
> Previously Mess With DNS was using a Postgres database. This was problematic because I only gave the Postgres machine 256MB of RAM, which meant that the database got OOM killed almost every single day. I never really worked out exactly why it got OOM killed every day, but that’s how it was.
Found this a little surprising - postgres is internet old - I'm pretty sure it was around at a time when physical servers might not have 256mb of ram?
Seems this should be possible to tune down still? (I mean, maybe not. Postgres 16 isn't postgres 6, and maybe I'm just getting old..)
- remram 2y agoPostgres can scale down, there are a few settings you can tweak: https://www.postgresql.org/docs/current/runtime-config-resource.html https://www.postgresql.org/docs/current/runtime-config-resou...
- zokier 2y agopgtune can generate config for 256MB server automatically, probably a good starting point: https://pgtune.leopard.in.ua/ https://pgtune.leopard.in.ua/
- whalesalad 2y agoMaintenance and vacuum is likely what’s causing this. Can definitely tune it down. 256mb is really not very much these days though.