v26 : more failsafety from permission issues, Partition analysis, IO data, etc

[jobinau]

• New failsafe code for environments where permission issues can prevent critical parts of the data collection,
  This improves the user experience of those who use the script against managed services like Aurora, where many functionalities are not compatible with PostgreSQL.
• Dropped the support for psql version PG 10 or older, exit with message gracefully if an older version of psql is used
  PostgreSQL server can be of PG 10, But the client (psql) needs to be minimum PostgreSQL
• Now parallel workers are clearly reported in the 'client` section of the report referring the Parent PID
• Now, the session level popup show the TLS version used and Parallel workers, if any
• Report Blocker sessions in the Popup similar to the Victim reporting.
• Code Refactoring
  Code quality improvement + fix for JSON handling using a dedicated function updateJson is introduced. This fixes some of the syntax highlighting in code editors and
• New item in the report for listing partitioned tables
• New Net/Delay calculation at database level as part of analysis data
• New footer for DB time analysis info with CPU usage in terms of CPU cores
• Net/Delay calculation summary to the footer of the DBTime analysis.
• Partitioned tables are marked with names and popup info contains the parent table info
• Additional analysis query to get PIDs with Net/Delays
• Fixes for the duration calculation, which was affecting the problem highlights at the session level, Added new minor releases list and removed PostgreSQL 11 from the list
• Indexes that are neither used on Primary nor on Replica/Standby
• PG 16 specific improvements. 1. Last use information per table and indexes, 2. IO Statistics Summary
• New analysis query on IO statistics
• Multiple CSS fixes, including font-weight getting inherited from the cell, UI improvement to give clear message on Popup, Bug fix for HBA rule query if someone specifies the hostname instead of IP in the address field
• Cleanup SQL statements from analysis_queries which are no longer relevant

---

This discussion was created from the release v26 : more failsafety from permission issues, Partition analysis, IO data, etc.