Guardioz blogNotes on PostgreSQL, reliability, and why we're building Guardioz.https://guardioz.com/blog.html2026-10-02T00:00:00ZGuardiozhttps://guardioz.com/The logging setting that slows down new connectionshttps://guardioz.com/blog/log-hostname-explained.html2026-10-02T00:00:00Z2026-10-02T00:00:00Zlog_hostname does not add the client to PostgreSQL's log - %h does. It adds a DNS lookup to every new connection. We measured what that costs.max_wal_size, explainedhttps://guardioz.com/blog/max-wal-size-explained.html2026-07-20T00:00:00Z2026-07-20T00:00:00Zmax_wal_size gives PostgreSQL's transaction log a size budget. Too small, and the server writes the same data again and again. How it works and how to tune it.Why we're building Guardiozhttps://guardioz.com/blog/why-we-are-building-guardioz.html2026-06-22T00:00:00Z2026-06-22T00:00:00ZPostgreSQL keeps the business running. When it slows down, someone has to find out why - and it's rarely a dedicated DBA. A short manifesto on the gap between a symptom and a decision.