From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: raghshr1351@gmail.com
Subject: BUG #18790: Pg_stat_statements doesn't track schema.
Date: Wed, 29 Jan 2025 19:10:33 +0000
Message-ID: <18790-2d0185ef5a47fca9@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 18790
Logged by: Raghvendra Mishra
Email address: raghshr1351@gmail.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?
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-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, raghshr1351@gmail.com
Subject: Re: BUG #18790: Pg_stat_statements doesn't track schema.
In-Reply-To: <18790-2d0185ef5a47fca9@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox