BUG #18790: Pg_stat_statements doesn't track schema.

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: raghshr1351(at)gmail(dot)com
Subject: BUG #18790: Pg_stat_statements doesn't track schema.
Date: 2025-01-29 19:10:33
Message-ID: 18790-2d0185ef5a47fca9@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 18790
Logged by: Raghvendra Mishra
Email address: raghshr1351(at)gmail(dot)com
PostgreSQL version: 17.0
Operating system: Linux
Description:

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?

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Masahiko Sawada 2025-01-29 19:13:26 Re: BUG #18789: logical replication slots are deleted after failovers
Previous Message Laurenz Albe 2025-01-29 16:29:51 Re: Trying to ugrade from version 16.2 to 17