| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Global tables |
| Date: | 2024-05-27 05:43:30 |
| Message-ID: | CAKFQuwbRANnNss0bx71PhZiBtbHPESY96d4hV8pmLevaBeGfsQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Sunday, May 26, 2024, Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com> wrote:
>
> With regards to system views/tables pg_stat_database, pg_stat_activity,
>
> pg_stat_statements[…] provide cluster wide information and not specific
> to database.
>
The first two (and databases) indeed work that way, the documentation for
the pg_stat_statements extension indicate it is handled per-database.
> However views such as pg_stat_user_tables, pg_stat_user_indexes ..etc
> shows db specific information.
>
Yes, object-specific data that resides within a database gets isolated.
> So I want to know how do I identify where are all the views that shows
> cluster wide info or db specific?
>
The descriptions for each view make it clear what data they show. I’m
unaware of any metadata within the system to track and query this dynamic.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sathish Reddy | 2024-05-27 05:50:30 | Toast table infi |
| Previous Message | Kashif Zeeshan | 2024-05-27 05:30:56 | Re: Global tables |