Kristian Klausen authored Feb 26, 2021 and Jelle van der Waa committed Apr 08, 2021

Fix #263

Kristian Klausen authored Mar 07, 2021 and Jelle van der Waa committed Apr 07, 2021

unbound is only used if dns_servers is explicit set to 127.0.0.1, which
isn't the case for any of these systems.

Fix #234

Seems we run at about 5GB of cache. Let postgres assume it gets 4GB.

Bump the mem settings higher again, now that we know they're not the
cause. Also increase the maximum connection count.

This seems to be the cause for our memory leak.

https://www.postgresql.org/message-id/flat/16707-f5df308978a55bf8%40postgresql.org

Still seeing PostgreSQL session processes eating over 600M of private
memory. What's going on?

Less work_mem because this explodes easily. It's per-operation, which a
query can have multiple of, and also across multiple worker threads.

More shared_buffers and effective_cache_size as these are global.

It ran out of memory, with Postgres using a lot of RSS.

We switched for monitoring to prometheus so zabbix-agent is unwanted and
we don't want to accidently deploy it again.

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>