From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | sud <suds1434(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Alerting on memory use and instance crash |
Date: | 2025-10-08 16:22:27 |
Message-ID: | 9f175444-6bfc-4c6e-a609-e552d85c45a1@aklaver.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/8/25 08:42, sud wrote:
> 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?
1) When you say instance do you mean database?
2) Not all system tables/views are database only.
For instance:
https://www.postgresql.org/docs/current/catalog-pg-database.html
https://www.postgresql.org/docs/current/catalog-pg-auth-members.html
https://www.postgresql.org/docs/current/catalog-pg-authid.html
https://www.postgresql.org/docs/current/view-pg-roles.html
> 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
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | sud | 2025-10-08 18:58:11 | Re: Alerting on memory use and instance crash |
Previous Message | Ron Johnson | 2025-10-08 16:21:53 | Re: Alerting on memory use and instance crash |