Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vM1dJ-00Gt2U-32 for pgsql-admin@arkaria.postgresql.org; Thu, 20 Nov 2025 10:11:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vM1dH-000r6e-0m for pgsql-admin@arkaria.postgresql.org; Thu, 20 Nov 2025 10:11:19 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vM1dG-000r5Z-2g for pgsql-admin@lists.postgresql.org; Thu, 20 Nov 2025 10:11:19 +0000 Received: from mail-yw1-x1129.google.com ([2607:f8b0:4864:20::1129]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vM1d6-000Uwn-3C for pgsql-admin@postgresql.org; Thu, 20 Nov 2025 10:11:17 +0000 Received: by mail-yw1-x1129.google.com with SMTP id 00721157ae682-787eb2d86bfso6559057b3.2 for ; Thu, 20 Nov 2025 02:11:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1763633469; x=1764238269; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=0UgF4lN7dJHpRozhJYHjU7pgjTt2S+cAnxtwH8Oxds8=; b=BILToiQxCSGqSQSQESDfr3UDicrF7lLg4qh29uoAk/0NzsCHPm2PYTu0eyfAdZLwS9 TN1rfoIkbCrtq7AyhGguN4MzAcF+Rv+Bkwle7O1ExotTRyYSw30b3W3ae6FVfxyneh83 Eje+8viw4PVJ53C5CQGVd1BMKm8CYT5Pp/SN0NhuqF99a/Qb/Ii9XnQmpUvs7u2NOVMZ WweJ9czspOMth8vc9fulPJ6Z7ecx989NdmVo8Q82fHG1X5M5wKO/HLyYQae712UMpZgb POyIv/UdbVTCIC0ViA/HHaMxd4IMXy4JzrynCaM9P3zocGHg39Yl0Zpjtrfte7TNtQ1s 68YQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1763633469; x=1764238269; h=to:subject:message-id:date:from:mime-version:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=0UgF4lN7dJHpRozhJYHjU7pgjTt2S+cAnxtwH8Oxds8=; b=lO/yPyEMvbSMZ7WyRx4ILFmoiIvXlznMvlUlaOD9ZraJV8np1dtF175UW/h7ALfoIq fp4IVmAjB/kp+Qjxc4PhSWHfGoK761QJulWOaHgnCvXUkmaYgKlIkFdV3cOBm0wR8K7O MLcEKwIdd6qi/jsx0IplAQaY5TFYyKQvcEv9g2VQ5huZTyFqZtu4pHZq0or0k9VPEOLl QqWW7O58LqULE93iUhV7PRiWAO0SRHzwBifKjTNs3jBdwu+iMjYWETc3cmL4WNodz2+5 YfISxqTfuAMhdxaRSWrt+DicgXN07w9IGTZElX9GJdNZ7iH605FjAZCmJUzo2e+DNO+J RQMg== X-Gm-Message-State: AOJu0YwwQ79sw23vzk/5GOEI1+pajJ7j3ob1Gl36UjOc/9jOxNHBt09c MF9kMfbbrXjHYMdKnQYwb/JX6Qr9N0IXElZibt36JJV5UFBo15UY4b9k7LOqV7aDPXdHfzIM6bN 7WjakI63giRe1P1aUY0PG0hOQVO8De7pMnA== X-Gm-Gg: ASbGnct5ag6O5QOqPo8Vnph+J0uEeMdKBJCPWCNAEIpDw/9a1UVKKA5vMrT9iON9dQU U703BjfJlcQfJCSn9whMJpj2TSFIjZnnTgoB1sxrgv6i/xHEhC9FJ+2jYVIh6zqUvzKEfHrYtIr MsZNlL17JPlhdCliB3jwoQqx7RxFWfj4lrKAa1qyxDouMq0Wk78j7uekMgGXOAmVHJxQBOTgM+S tS8OOWNQkKeFVHKG7nFewXgeMFId8izMB9yrZ/7rE2EBrA5r+BjpquWsdHLNNEGC9wVlX9d+wMT Vwj55XtXO6oIhnQ5nk4QeOdlKubN X-Google-Smtp-Source: AGHT+IE1qu5a3V0fthBEKAdmqSPYbLCLxTPlpveE848kOXfLRrzkAYCuMtPSKrsu5YQG0nQCnDWaIK7r5znFGzF/BDA= X-Received: by 2002:a05:690c:a87:b0:786:506c:3cba with SMTP id 00721157ae682-78a79560985mr24917007b3.13.1763633468730; Thu, 20 Nov 2025 02:11:08 -0800 (PST) MIME-Version: 1.0 From: kamal deen Date: Thu, 20 Nov 2025 15:40:57 +0530 X-Gm-Features: AWmQ_bl6Bfe5Gu2iXC0WB3hpy6pamuiqV-8qVuIM9bnRdDR9ZCpyxnGtSweneuk Message-ID: Subject: Postgres Exporter 0.17.0 heavy default statement To: pgsql-admin@postgresql.org Content-Type: multipart/alternative; boundary="0000000000006af0ef064403eabd" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000006af0ef064403eabd Content-Type: text/plain; charset="UTF-8" Hi All, Is anyone had face swap/memory or resource usage issue due to postgres exporter. We have observed one default select query part of exporter metrics which is collecting some info from pg_stat_statment and calculating percentile.(looks like heavy query). Suspecting our prod environment was down due to that statement which caused heavy swap.noticed that this statement creating temp files (was written in log file before it was down). Pls advice if any one come across this issue and share if any fix is applied on this. Postgres Version 16 Exporter Version 0.17.0 OS : Linux Regards, SK --0000000000006af0ef064403eabd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi All,

Is a= nyone had face swap/memory or resource usage issue due to postgres exporter= .

We have observed one d= efault select query part of exporter metrics which is collecting some info = from pg_stat_statment and calculating percentile.(looks like heavy query). = Suspecting=C2=A0 our prod environment was down due to that statement which = caused heavy swap.noticed that this statement creating temp files (was=C2= =A0 =C2=A0written in log file before it was down).
<= br>
Pls advice if any one come across this issue and= share if any fix is applied on this.

Postgres Version 16
Exporter Version 0= .17.0
OS : Linux

Regards,
SK
--0000000000006af0ef064403eabd--