Re: BUG #18790: Pg_stat_statements doesn't track schema.

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: raghshr1351(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18790: Pg_stat_statements doesn't track schema.
Date: 2025-01-30 06:40:34
Message-ID: Z5se4quPTEONCNjE@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Jan 29, 2025 at 07:10:33PM +0000, PG Bug reporting form wrote:
> Currently, pg_stat_statment doesn't track the schema to which the query
> belongs. In the case of a multitenant database, it becomes hard to find a
> query belonging to which customer is the culprit. It could be solely an
> enhancement, so my question is, Is it useful to expose the schema name also?
> If yes can I contribute to add this support?

Objects from multiple schemas could be used in a single query. Even
if multiple schemas are tracked, I doubt that the cost of tracking
them is going to be really useful at this level for monitoring. Or
perhaps you have some specific use case in mind?
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Laurenz Albe 2025-01-30 07:54:19 Re: Bug in psql
Previous Message VASUKI M 2025-01-30 03:59:21 Fwd: BUG #18784: Bugs and BugTracking