Re: Alerting on memory use and instance crash
От | Ron Johnson |
---|---|
Тема | Re: Alerting on memory use and instance crash |
Дата | |
Msg-id | CANzqJaCpM18oHAYpZHk9cW=0zjxMGKLKZOPCi1eHGm4ssb4ZsA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Alerting on memory use and instance crash (sud <suds1434@gmail.com>) |
Ответы |
Re: Alerting on memory use and instance crash
|
Список | pgsql-general |
On Wed, Oct 8, 2025 at 2:58 PM sud <suds1434@gmail.com> wrote:
[snip]
Do you mean in normal Postgres it's alway a single instance/memory and single storage attached? then I also do not see any such cluster level views in aws aurora postgres too?
Yup.
Pardon if it's a silly one to ask.
A Google for "what's the difference between Oracle and Postgresql" _might_ help. I've never done that, so don't know what you'll find.
As far as how Aurora works... you need to ask AWS. It's been too heavily modified for a list dedicated to pure/unmodified Postgresql to help.
On Wed, Oct 8, 2025 at 9:52 PM Adrian Klaver <adrian.klaver@aklaver.com> wrote: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.klaver@aklaver.com
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
В списке pgsql-general по дате отправления: