Skip to content

Releases: percona/pg_stat_monitor

2.0.4

12 Dec 16:27
75f86f5
Compare
Choose a tag to compare

GH-646 - Resolving a possible issue that could lead to pg_stat_monitor deadlocking in pgsm_store.

2.0.3

14 Nov 12:37
0a8ac38
Compare
Choose a tag to compare

Bugs Fixed
GH-425 - pg_stat_monitor crashes PostgreSQL if Citus library is loaded

2.0.2

12 Sep 17:48
Compare
Choose a tag to compare

Release highlights
This release adds support for PostgreSQL version 16 by resolving compilation and API change issues.

2.0.1

25 May 14:46
Compare
Choose a tag to compare

Release highlights
This release fixes the server crash when running pgsm_enable_query_plan is enabled, addresses the incorrect behaviour with the non-default number of buckets configured, and improves the memory context handling for pg_stat_monitor.

Bugs Fixed
PG-613 - Fixed the issue with segmentation fault error when the query plan is enabled on large queries.
PG-624 - Fixed the server crash when running pgbench with pg_stat_monitor loaded by improving the handling of the dynamic number of buckets.

2.0.0

24 Apr 10:00
Compare
Choose a tag to compare

Improvements

PG-310: Bucket is “Done” vs still being current/last

PG-400: Add timezone in datetime columns in pg_stat_monitor view.

PG-435: PostgreSQL 15 Support by adding newly introduced columns

PG-488: Update query buffer overflow management to use dynamic shared memory

PG-543: PostgreSQL's pg_stat_statements compatible view.

PG-545: Same query text should generate same queryid

PG-569: Make all data types of pg_stat_monitor view compatible with pg_stat_statements

PG-586: CPU and user timing should be captured for utility statements as well

PG-588: Fix missing query and query normalization issue; rearchitect pg_stat_monitor

PG-606: New GUC required for enabling/disabling of pgsm_query_id calculation

PG-607: Allow histogram to track queries in sub-ms time brackets

Bug Fixes

PG-306: bucket_start_time - TEXT vs TIMESTAMP?

PG-320: Remove state/state_code fields from pg_stat_monitor_view.

PG-321: Remove redundant cmd_type/cmd_type_text columns in pg_stat_monitor view.

PG-354: Remove pg_stat_monitor_settings view

PG-373: Remove wal fields for PG12 and below

PG-518: Internal Functions should NOT be visible in PGSM API.

PG-579: Querying pg_stat_monitor view crashes the server when pg_stat_monitor.so is not configured in shared_preload_libraries

PG-582: blk_read_time and blk_write_time are not being rounded.

PG-583: Rounded time based values are not consistent

PG-597: Remove rounding off for floating point values

PG-569: Make all data types of pg_stat_monitor view compatible with pg_stat_statements

1.1.1

08 Nov 18:06
ce12d56
Compare
Choose a tag to compare

Bugs Fixed

PG-520: pg_stat_monitor does not work with PostgreSQL15

1.1.0

06 Sep 19:40
22ad698
Compare
Choose a tag to compare

Improvements

PG-474: Make pg_stat_monitor compiled with CLANG
PG-159: Change the bucket start time scheme to align with the bucket time size
PG-293: Add the ability to control features added on top of pg_stat_monitor using GUC (Grand Unified Configuration) parameters
PG-300: Improve compatibility with PMM by making QueryIDs persistent for the same queries across different buckets and regardless of the node / client a query is executed on.
PG-362: Fix the pgsm_normalized_query default value to provide query examples in the pg_stat_monitor view by default.
PG-439: Remove warning of comparison of unsigned enum expression

Bugs Fixed

PG-221: Fixed the issue with pg_stat_monitor crashing when querying JSON with parallel workers enabled
PG-289: Fixed the issue with pg_stat_monitor failing to build on C11 compilers by removing 'for' loop initial declarations
PG-449: Fix comments visibility by correcting the behavior of the pgsm_extract_comments parameter
PG-453: Fixed query normalization for INSERT statements in PostgreSQL 13 and earlier versions
PG-455: Fixed the issue with data collection for any value specified for pgsm_bucket_time parameter within the min / max range

1.0.1

26 May 19:05
8330ecd
Compare
Choose a tag to compare

Bugs Fixed

PG-382: Histogram default settings changed to prevent the PostgreSQL server to crash

PG-417: Addressed security vulnerabilities to prevent an attacker from precreating functions

DISTPG-427: Fixed the issue with the extensions not working when pg_stat_monitor is enabled by replacing the return with goto exit for the pgsm_emit_log_hook function

1.0.0

03 May 09:00
d26a5a3
Compare
Choose a tag to compare

Changed

  • PG-380: Bump version from 1.0.0-rc.2 to 1.0.0.

1.0.0-rc.2

21 Apr 17:57
afd2e1d
Compare
Choose a tag to compare

1.0.0-rc.2

Improvements

PG-331: Changed the default value for the pg_stat_monitor.pgsm_query_max_len parameter from 1024 to 2048 for better data presentation in PMM

PG-355: Changed the collection of sys_time and user_time metrics so that they are now presented as an accumulative value

PG-286: Improved pg_stat_monitor performance by decreasing the overhead by more than 50%.

PG-267: Added test case to verify histogram feature

PG-359: Documentation: updated the pg_stat_monitor_settings view reference.

PG-344: Documentation: Updated the extensions order and behavior with data collection for PostgreSQL 14.

PG-358: Documentation: data display of ** blk ** and ** wal ** columns when both pg_stat_monitor and pg_stat_statements are loaded together.

Bugs Fixed

PG-350: Fixed bucket time overflow

PG-338: Fixed query calls count by setting the default value for pg_stat_monitor.pgsm_track to top.

PG-291: Fixed calls count.

PG-325: Fixed deadlock that occurred when the query length exceeded the pgsm_query_max_len value.

PG-326: Added validation for pgsm_histogram_min and pgsm_histogram_max ranges

PG-329: Fixed creation of pg_stat_monitor_errors view on SQL files.

PG-296: Fixed issue with the application name not displaying in the view when changed.

PG-290: Fixed issue with PostgreSQL crashing after enabling debug log level and when pg_stat_monitor is enabled.

PG-166: Fixed issue with displaying the actual system time values instead of NULL

PG-369: Fixed issue with incorrect wal_bytes values for PostgreSQL 11 and 12 that caused Query Analytics failure in PMM by ignoring the WalUsage variable value for these versions.