)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":36080,"name":"Erkin Mussurmankulov","display_name":"Eric","email":"erkin.mussurmankulov@ps.kz","username":"mongoose404","status":"PS Cloud services employee"},"change_message_id":"b08a20d24d45bf854db202041aeb915eb0b3fd92","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"bb4a8e34_bd7ff1b9","updated":"2026-08-10 13:55:39.000000000","message":"Hello, Wu!\nCan you please check this trivial MR?\n\nWe recently hit an issue with long reverse DNS lookups during SQL client connections to the PostgreSQL database. All new incoming connections took exactly 8+ seconds.\n\nProbably it\u0027s related to some bugs in the DNS library introduced in recent OS updates, which we can\u0027t control.\n\nSo the most obvious and quickest solution is to remove the `localhost` record from pg_hba, which would set PostgreSQL to disable DNS lookups altogether.\nRemoving this record on live production PostgreSQL servers manually and doing `pg_reload_conf()` or `database instance restart` resolves this issue.","commit_id":"c39d17f969705125ce2493a8426787200199e7c2"},{"author":{"_account_id":36080,"name":"Erkin Mussurmankulov","display_name":"Eric","email":"erkin.mussurmankulov@ps.kz","username":"mongoose404","status":"PS Cloud services employee"},"change_message_id":"063e70d3f302675a1c8c17c929c8aef5a464c9b4","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"6e7a71a6_08532904","updated":"2026-08-09 16:35:52.000000000","message":"recheck","commit_id":"c39d17f969705125ce2493a8426787200199e7c2"}]}