Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

pg_stat_monitor: Need to provide configurations for pg_stat_monitor to act like pg_stat_statments

Description

In ScaleX19 people were asking if there is any chance we can configure pg_stat_monitor to act like pg_stat_statments. They have applications which are working with pg_stat_statments and that application should work on pg_stat_monitor.

 

Let's define what we mean by pg_stat_statements behaviour.

How to document

None

How to test

None

Smart Checklist

Activity

Show:

Hamid Akhtar January 30, 2023 at 8:49 AM

We've ( , , ) have decided to not match pg_stat_statements configuration for this release.

Ibrar Ahmed December 19, 2022 at 2:46 PM

 We have done some analysis on that and found that it will create more confusion if we change the behaviour of pg_stat_monitor to pg_stat_statment. There are other ways to change the column name of pg_stat_monitor to pg_stat_statments, but it has some issues.

 

1 - PMM needs to change the name and comments at their end.

2 - PMM need to run some sub-queries to generate readable data; for example, if we expose dbid instead of the database name, then PMM need to query the database for the database name based on dbid. 

3 - If we add duplicate name columns, it becomes a readability issue and creates confusion.

 

I am dropping that idea now and will discuss it in more detail.

Won't Do

Details

Assignee

Reporter

Labels

Components

Fix versions

Priority

Parent

Smart Checklist

Created August 6, 2022 at 7:49 PM
Updated July 10, 2024 at 10:58 AM
Resolved January 30, 2023 at 8:49 AM