Skip to content

1.0.0-rc.2
Compare
Choose a tag to compare
@ibrarahmad ibrarahmad released this 21 Apr 17:57
1.0.0-rc.2
afd2e1d
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

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.

Assets 2
Loading