mirror of
https://github.com/percona/pg_stat_monitor.git
synced 2026-02-04 14:06:20 +00:00
de66ef0fce
This bug uncovered serious issues with how the data was being stored by PSGM. So it require a complete redesign. pg_stat_monitor now stores the data locally within the backend process's local memory. The data is only stored when the query completes. This reduces the number of lock acquisitions that were previously needed during various stages of the execution. Also, this avoids data loss in case the current bucket changes during execution. Also, the unavailability of jumble state during later stages of executions was causing pg_stat_monitor to save non-normalized query. This was a major problem as well. pg_stat_monitor specific memory context is implemented. It is used for saving data locally. The context memory callback helps us clear the locally saved data so that we do not store it multiple times in the shared hash. As part of this major rewrite, pgss reference in function and variable names is changed to pgsm. Memory footprint for the entries is reduced, data types are corrected where needed, and we've removed unused variables, functions and macros. This patch was mutually created by: Co-authored-by: Hamid Akhtar <hamid.akhtar@percona.com> Co-authored-by: Muhammad Usama <muhammad.usama@percona.com>
21 lines
475 B
SQL
21 lines
475 B
SQL
CREATE EXTENSION pg_stat_monitor;
|
|
|
|
CREATE TABLE t1(a int);
|
|
CREATE TABLE t2(b int);
|
|
INSERT INTO t1 VALUES(generate_series(1,1000));
|
|
INSERT INTO t2 VALUES(generate_series(1,5000));
|
|
|
|
SELECT pg_stat_monitor_reset();
|
|
SELECT * FROM t1;
|
|
SELECT * FROM t2;
|
|
|
|
SELECT * FROM t1 LIMIT 10;
|
|
SELECt * FROM t2 WHERE b % 2 = 0;
|
|
|
|
SELECT query, rows FROM pg_stat_monitor ORDER BY query COLLATE "C";
|
|
SELECT pg_stat_monitor_reset();
|
|
|
|
DROP TABLE t1;
|
|
DROP TABLE t2;
|
|
DROP EXTENSION pg_stat_monitor;
|