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.94.2) (envelope-from ) id 1v6WJ6-005qWi-Hb for pgsql-general@arkaria.postgresql.org; Wed, 08 Oct 2025 15:42:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1v6WJ4-00BAmS-36 for pgsql-general@arkaria.postgresql.org; Wed, 08 Oct 2025 15:42:23 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1v6WJ3-00BAmI-MR for pgsql-general@lists.postgresql.org; Wed, 08 Oct 2025 15:42:22 +0000 Received: from mail-pl1-x62b.google.com ([2607:f8b0:4864:20::62b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1v6WJ2-0013gf-0d for pgsql-general@lists.postgresql.org; Wed, 08 Oct 2025 15:42:22 +0000 Received: by mail-pl1-x62b.google.com with SMTP id d9443c01a7336-27edcbbe7bfso117394925ad.0 for ; Wed, 08 Oct 2025 08:42:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1759938137; x=1760542937; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=xrk2J7vdsK9H2nzktD5E4exAzrFEmndcKYgqRmv8K8U=; b=OirwsZqOL/mrmKU/weTID+FUOSAvx4e60OyfT34r/n4LkzOMFemjUfd5NxeJ0bAU+w mylQenDmBf/zczDVnyVAZuTfxRim3bz9VFC0yb9z0JM4oiturEBYUv+ZrVoP/ewWfcJn Im9FCXziSOn3wgkxeH2/HdtdCyIABnnMJoqkRaVYD7cmN0/5ji4W6ZrdG2odYcdtansh JUFTcDYxGQCh5lKOQGpOU3HvK/IhRNkIQZJaqZa34ZMGZ0p96CgoPSLT5u/b6Fww3tmm YGmgjsb7559tQIXw6h9mgiJF+69OiX+V8DfLgYE5oQ2oIKyLUjKAlnfOITJe5WPfdpy8 w3RA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1759938137; x=1760542937; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=xrk2J7vdsK9H2nzktD5E4exAzrFEmndcKYgqRmv8K8U=; b=WjtaA89EUwnZNqgn9ZS7uXtP04GRfj4UjsDbT/ZAVh4yjBCwItjfzswqFM1XFUJwvj ycxdcFjfD+jYqFF5NPS/p4LsTe1tcZxhFcKLDrOiMBsRX3vNlSqpPAdXCc5RzbQIQS/Z UYnAkZs10yichaXalWGeISBx0DOFPqBs3FpeqSVMAK/xhcvzTYrmltE/ku3vXrfYu62z xF3YbeqmreGFKiIqj4foHJr1QoL8y/DuArQNp/XxbN6G/Igm3v1r3R+X36LLiUaozlYO BqpEbgwZ+I87trtyB9LmTjX9s2Bd4C7BL/QO5K0hufl6MCiQ+51reaJnWanXLAGHNTUF VhwQ== X-Gm-Message-State: AOJu0Yy0PEn4slnchpDRLdrRFSZeQ3mU7Q+2TD0ABta8gcF+I7zAZ23m 7ZKt+csPeHqcEjqt8rXZO65Xr73/JnqpsJx8TUDr3Qmk/EkXnMihCc75t3pMLh0Qq49n5oTy4cp E5BAjs80AUdLS5k2RccVqRpnFILuOzmnLezTY X-Gm-Gg: ASbGncvLa6oOx7tjJZqmKASE49uap173XXigi/GLaX0ZdjII7/mrwAxvtm4RLMHcOWl JhNFoAY3sSpY13nBGaz64eghJVO/xK7C6LzEFW9cf8S8D/BaEsuo5aUaIDvn0w8SSdIhTU/g5uY yrgfhoXDEifNsRVuSvxRP7loYAWtAbMTtsTmEQ2sKkcU/q4Tmc+v85iECECdibDQo5dSOQVu8yz mMix4S+33yZ9TFYKwHA7qqYcc8s8GwILvovHXoe0mbMJ9v1yZuptzDbO6PSkWNmNkvi8XYy X-Google-Smtp-Source: AGHT+IEVkHqVmSAjkzKFy0vlpfsj6HgBRelwNkzaBwmqBBvebJEEVFjmwKe7X3RlELaKmz2rJbb2V4wqx5Yu17M2nCM= X-Received: by 2002:a17:903:2350:b0:274:aab9:4ed4 with SMTP id d9443c01a7336-29027312ffamr52476605ad.57.1759938137158; Wed, 08 Oct 2025 08:42:17 -0700 (PDT) MIME-Version: 1.0 From: sud Date: Wed, 8 Oct 2025 21:12:05 +0530 X-Gm-Features: AS18NWDvJvs3V1bhenRRcBz4rfFUgliidB5EygRen_yILkJBtIUkElI0UMDhUX4 Message-ID: Subject: Alerting on memory use and instance crash To: pgsql-general Content-Type: multipart/alternative; boundary="0000000000007dfa3f0640a78774" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000007dfa3f0640a78774 Content-Type: text/plain; charset="UTF-8" Hi Experts, It's postgres version 16. I have two questions on alerting as below. 1)If we want to have alerting on any node/instance that gets crashed :- In other databases like Oracle the catalog Views like "GV$Instance" used to give information on whether the instances are currently active/down or not. But in postgres it seems all the pg_* views are instance specific and are not showing information on the global/cluster level but are restricted to instance level only. So is there any other way to query the pg_* views to have alerts on the specific instance crash? 2)Is there a way to fetch the data from pg_* view to highlight the specific connection/session/sqls which is using high memory in postgres? Appreciate your guidance. Regards Sud --0000000000007dfa3f0640a78774 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Experts,

It's postgres version 16. I have tw= o questions on alerting as below.

1)If we want to have alerting= on any node/instance that gets crashed :- In other databases like Oracle t= he catalog Views like "GV$Instance" used to give information on w= hether the instances are currently active/down or not. But in postgres it s= eems all the pg_* views are instance specific and are not showing informati= on on the global/cluster level but are restricted to instance level only. S= o is there any other way to query the pg_* views to have=C2=A0alerts on the= specific instance crash?
2)Is there a way to fetch the data from pg_* v= iew to highlight the specific connection/session/sqls which is using high m= emory in postgres?

Appreciate your guidance.

Regards
Sud
--0000000000007dfa3f0640a78774--