| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | "Subramanian,Ramachandran" <ramachandran(dot)subramanian(at)alte-leipziger(dot)de>, "depesz(at)depesz(dot)com" <depesz(at)depesz(dot)com> |
| Cc: | "pgsql-novice(at)lists(dot)postgresql(dot)org" <pgsql-novice(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: AW: AW: Is it possible to turn on pg_stat_extensions at a database level |
| Date: | 2026-03-13 06:58:39 |
| Message-ID: | b0d10cdd0a9f473803b08c1a6c90e9998a43724d.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On Fri, 2026-03-13 at 05:54 +0000, Subramanian,Ramachandran wrote:
> Coming from the mainframe world, we always assume that there is a lot of
> CPU/IO expense to monitor and collect statistics from unnecessary Databases.
>
> This is why I wanted the collection of the statitstics itself to be restricted
> to just one Database.
Ok, now you know that you cannot get it.
I doubt that there are databases where monitoring is unnecessary:
- if there is nothing doing in that database, that won't be a lot of statistics
to collect
- if there is a lot going on in that database, the load will be noteworthy
and can affect your other, necessary, databases in the same cluster, so
you need the statistics to diagnose such problems
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2026-03-13 07:04:19 | Re: A vexing problem with LDAP |
| Previous Message | Subramanian,Ramachandran | 2026-03-13 06:57:29 | A vexing problem with LDAP |