public inbox for pgsql-novice@postgresql.org
help / color / mirror / Atom feedFrom: Subramanian,Ramachandran <ramachandran.subramanian@alte-leipziger.de>
To: depesz@depesz.com <depesz@depesz.com>
Cc: pgsql-novice@lists.postgresql.org <pgsql-novice@lists.postgresql.org>
Subject: AW: Is it possible to turn on pg_stat_extensions at a database level
Date: Thu, 12 Mar 2026 09:33:29 +0000
Message-ID: <959ecf128e514007a7558febe8b76e35@alte-leipziger.de> (raw)
In-Reply-To: <abKHnbVxwkrGL1Fb@depesz.com>
References: <c263728956fa4dc2b4c00bd3822d497b@alte-leipziger.de>
<abKHnbVxwkrGL1Fb@depesz.com>
Yes, I mistyped .
Pg_stat_statements.
I meant to ask if the extension can be created only for one database, so that the details from the other databases are not recorded.
LG
Ram
Freundliche Grüße
i. A. Ramachandran Subramanian
Zentralbereich Informationstechnologie
Alte Leipziger Lebensversicherung a.G.
Hallesche Krankenversicherung a.G.
Alte Leipziger Lebensversicherung a.G., Alte Leipziger-Platz 1, 61440 Oberursel
Vors. des Aufsichtsrats: Dr. Walter Botermann · Vorstand: Christoph Bohn (Vors.), Dr. Jürgen Bierbaum (stv. Vors.), Frank Kettnaker, Dr. Jochen Kriegmeier, Alexander Mayer, Christian Pape, Wiltrud Pekarek, Udo Wilcsek
Sitz Oberursel (Taunus) · Rechtsform VVaG · Amtsgericht Bad Homburg v. d. H. HRB 1583 · USt.-IdNr. DE 114106814
Hallesche Krankenversicherung a.G., Löffelstraße 34-38, 70597 Stuttgart
Vors. des Aufsichtsrats: Dr. Walter Botermann · Vorstand: Christoph Bohn (Vors.), Dr. Jürgen Bierbaum (stv. Vors.), Frank Kettnaker, Dr. Jochen Kriegmeier, Alexander Mayer, Christian Pape,
Wiltrud Pekarek, Udo Wilcsek
Sitz Stuttgart · Rechtsform VVaG · Amtsgericht Stuttgart HRB 2686 · USt.-IdNr. DE 147802285
Beiträge zu privaten Kranken- und Pflegekrankenversicherungen unterliegen nicht der Versicherungsteuer (§ 4 Nr. 5 VersStG) · Versicherungsleistungen sowie Umsätze aus Versicherungsvertreter-/Maklertätigkeiten sind umsatzsteuerfrei
Die Pflichtangaben der ALH Gruppe gemäß § 35a GmbHG bzw. § 80 AktG finden Sie hier: https://www.alte-leipziger.de/impressum
______________________
ALH Gruppe
Alte Leipziger-Platz 1, 61440 Oberursel
Tel.: +49 (6171) 66-4882
Fax: +49 (6171) 66-800-4882
E-Mail: ramachandran.subramanian@alte-leipziger.de
www.alte-leipziger.de
www.hallesche.de
-----Ursprüngliche Nachricht-----
Von: depesz@depesz.com <depesz@depesz.com>
Gesendet: Donnerstag, 12. März 2026 10:30
An: Subramanian,Ramachandran IT-md-db <ramachandran.subramanian@alte-leipziger.de>
Cc: pgsql-novice@lists.postgresql.org
Betreff: Re: Is it possible to turn on pg_stat_extensions at a database level
On Thu, Mar 12, 2026 at 08:54:04AM +0000, Subramanian,Ramachandran wrote:
> I have turned on pg_stat_extension for an instance. This instance has many databases. I want to confine the statistics to only one database.
> Is it possible to do this?
Do you mean pg_stat_statements?
If no - sorry, never heard of pg_stat_extension.
If yes - nope. stats are global. You can limit what you're analysing from stats by adding appropriate where condition, like:
SELECT
*
FROM
pg_stat_statements AS pss
JOIN pg_database AS d ON pss.dbid = d.oid WHERE
d.datname = 'postgres';
Best regards,
depesz
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-novice@postgresql.org
Cc: ramachandran.subramanian@alte-leipziger.de, depesz@depesz.com, pgsql-novice@lists.postgresql.org
Subject: Re: AW: Is it possible to turn on pg_stat_extensions at a database level
In-Reply-To: <959ecf128e514007a7558febe8b76e35@alte-leipziger.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox