| From: | vrms <vrms(at)netcologne(dot)de> |
|---|---|
| To: | pgsql-novice(at)lists(dot)postgresql(dot)org |
| Subject: | Re: AW: Is it possible to turn on pg_stat_extensions at a database level |
| Date: | 2026-03-17 10:59:50 |
| Message-ID: | c59dce06-e710-4063-afe7-a5c527d10d24@netcologne.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
As far as I understand the matter the extension starts gathering
statistical information on statements in all databases of a cluster once
'pg_stat_statments' is mentioned in the 'shared_preload_libraries'
setting (including all overhead coming with it) and does nothing without it.
CREATE EXTENSION pg_stat_statements just adds the view to look at these,
based on the WHERE clauses mentioned already.
It does not even have to be created inside that database you want to use
it for.
all best
Gunnar
On 3/12/26 10:33, Subramanian,Ramachandran wrote:
> 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(dot)subramanian(at)alte-leipziger(dot)de
> www.alte-leipziger.de
> www.hallesche.de
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: depesz(at)depesz(dot)com <depesz(at)depesz(dot)com>
> Gesendet: Donnerstag, 12. März 2026 10:30
> An: Subramanian,Ramachandran IT-md-db <ramachandran(dot)subramanian(at)alte-leipziger(dot)de>
> Cc: pgsql-novice(at)lists(dot)postgresql(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Subramanian,Ramachandran | 2026-03-20 06:33:32 | Replication Testing- How to introduce a Lag |
| Previous Message | Laurenz Albe | 2026-03-13 07:04:19 | Re: A vexing problem with LDAP |