pg_reports 0.5.4 → 0.6.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e98f6b7de8825ba0c851061a0d5e6f341986b9f710d594a9079a0a220c86f043
-  data.tar.gz: 713c08469b6c9d7aaea22c133e838cc73ac294acc64bba8fb21fa094c3680745
+  metadata.gz: 77275298b8ef6a1dba986e9b47849d1685e2d09cacdd64e3b086b20ab403574c
+  data.tar.gz: 893da425321112adf5d4f9944fb72028898c77119ec95ad92d27c21681a80a0e
 SHA512:
-  metadata.gz: 8e0380c79d58828741eb17529e23272bb3e6fcafcfa7193e2a378e436a55b72b9e5be73e06ec3709836620e50ae704f7213cda83146fec489919695f364d7375
-  data.tar.gz: 7c5fdd5d289836e04a7b907d88e191e7a270d7bfffbc056230cc1469c4a83ff434e5fbf55dc0c49b6f84bdc2fc949e7b6858627e2e9387f0d9d7c22db423e77e
+  metadata.gz: c99a83908899a5896734b7025b4b593dad0c0d4045b9578e1912ccb332aa9f29dcb0c1e79fe69a403f4a248e99a540fc1b0627af44d7ddc1c1c889c738c1ffa7
+  data.tar.gz: 4ff3fe8ae5a907dee4a6eb9186adb1e9819d49e62c84c7447c49999dd2c4f09d01cd962711461437f18f1853ba1c3ea9b226af5a822a373034f61f93521ef1f5

data/CHANGELOG.md

@@ -7,6 +7,75 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.6.1] - 2026-04-24
+
+### Added
+
+- **8 new reports** — 4 dead-schema/write-amplification reports plus 4 Rails-schema-consistency reports:
+  - `unused_columns` (Schema Analysis) — columns with `pg_stats.n_distinct = 1`, indicating no `UPDATE` has ever changed them since creation. Strong signal that the application code no longer references the column.
+  - `always_null_columns` (Schema Analysis) — nullable columns where ~100% of rows are NULL. Companion to `unused_columns` from a different angle.
+  - `update_hotspots` (Tables) — tables with high `updates_per_row` (same rows rewritten repeatedly) or low `hot_update_pct` (indexed columns being updated, defeating HOT). Includes refactor guidance: split hot/cold columns, event-log tables, write batching, fillfactor tuning.
+  - `unused_tables` (Tables) — tables with zero `seq_scan + idx_scan` since the last stats reset. Surfaces `db_stats_since` so you know how much history the verdict rests on.
+  - `polymorphic_without_index` (Schema Analysis) — polymorphic `belongs_to` associations whose `(*_type, *_id)` pair has no composite index. With table growth, association loads turn into seq scans.
+  - `counter_cache_issues` (Schema Analysis) — `belongs_to ..., counter_cache: ...` declarations whose target column is missing on the parent. Counter is silently broken — writes go nowhere, reads return nil/zero.
+  - `soft_delete_without_scope` (Schema Analysis) — tables with a `deleted_at` / `discarded_at` / `archived_at` column whose model has no scope filtering soft-deleted rows. Plain queries leak deleted data into reports, indexes, exports.
+  - `orphan_tables` (Schema Analysis) — DB tables with no corresponding Rails model class. Classified as `join_table_candidate` (likely legitimate HABTM), `join_model_without_class` (probably should be a model), or `legacy` (the interesting ones).
+- New problem keys: `unused_column`, `always_null_column`, `hot_rows`, `low_hot_update`, `unused_table`, `polymorphic_no_index`, `counter_cache_missing_column`, `soft_delete_unprotected`, `orphan_table_legacy`.
+- Full i18n for all new reports (en/ru/uk).
+- **Full UI localization (en/ru/uk).** All dashboard chrome — buttons, modals, toasts, status badges, metric labels, filter labels, error messages, monitoring panels — now reads from a new `pg_reports.ui.*` locale namespace (183 keys per language). Plus three sibling namespaces resolved at access time from `Dashboard::ReportsRegistry` and `ReportDefinition#filter_parameters`:
+  - `pg_reports.categories.*` — the 6 dashboard category names (Queries / Indexes / Tables / Connections / System / Schema Analysis).
+  - `pg_reports.reports.<name>.{name, description}` — short name and one-line description for all 47 reports shown in the dashboard listing.
+  - `pg_reports.parameters.<name>.{label, description}` plus `threshold_label`/`threshold_description` templates for filter inputs.
+  Previously only the per-report long-form documentation was translated; the surrounding UI was hardcoded English regardless of `I18n.locale`.
+  - Added `window.PG_REPORTS_I18N` injected by the layout (`I18n.t('pg_reports.ui').to_json`) so client-side JS strings (toasts, dynamically rendered HTML, EXPLAIN output, IDE menu, query monitor feed) all respect the active locale.
+  - `<html lang>` now reflects `I18n.locale` instead of being hardcoded to `en`.
+  - Controller-level error/success messages (`reset_statistics`, `live_metrics`, `explain_analyze`, `execute_query`, `create_migration`, etc.) now use `I18n.t`.
+
+### Changed
+
+- `module_generator` now camelizes multi-word module names (`schema_analysis` → `SchemaAnalysis`) so YAML-defined reports can live under multi-word modules. Previously only single-word modules worked via auto-generation.
+- `NEW` badge moved off the seven 0.6.0 reports onto the four added in this version.
+
+## [0.6.0] - 2026-04-11
+
+### Added
+
+- **7 new reports** covering previously undetected PostgreSQL problems:
+  - `inefficient_indexes` — indexes with high read-to-fetch ratio indicating misaligned composite index column order
+  - `fk_without_indexes` — foreign keys on child tables missing a supporting index, causing seq scans on parent DELETE/UPDATE
+  - `index_correlation` — low physical correlation between index order and row order, causing excessive random I/O on range scans
+  - `temp_file_queries` — queries spilling intermediate results to disk due to insufficient `work_mem` (requires pg_stat_statements)
+  - `tables_without_pk` — tables missing primary keys, which breaks logical replication and causes ORM issues
+  - `wraparound_risk` — transaction ID age proximity to the 2-billion wraparound limit that triggers emergency PostgreSQL shutdown
+  - `checkpoint_stats` — checkpoint frequency and background writer metrics with PostgreSQL 17+ support
+- **AI Prompt Export** — "Copy Prompt" button in the Export dropdown generates a ready-to-paste prompt for AI coding assistants (Claude Code, Cursor, Codex) with problem description, fix instructions, and actual report data as examples. Available for 28 actionable reports.
+- **Compatibility warnings** — the gem now warns at boot if Ruby, Rails, or PostgreSQL versions are below minimum supported (Ruby 2.7, Rails 5.0, PostgreSQL 12)
+- **`inefficient_index_threshold_ratio`** configuration option (default: 10) for the inefficient indexes report
+- Full i18n support for all new reports in English, Russian, and Ukrainian
+
+### Fixed
+
+- **Critical: infinite recursion in Query Monitor with database-backed cache stores** (SolidCache, ActiveRecord Cache Store) — `handle_sql_event` called `Rails.cache.read()` on every SQL event to check `enabled` state, which with DB-backed caches generated new SQL events, creating an infinite loop. Fixed by storing monitoring state in local instance variables (`@enabled`, `@session_id`) and syncing from cache only at initialization. Added reentrancy guard as additional safety net. (Reported via [PR #7](https://github.com/deadalice/pg_reports/pull/7))
+- **`checkpoint_stats` compatibility with PostgreSQL 17+** — checkpoint columns were moved from `pg_stat_bgwriter` to `pg_stat_checkpointer` with renamed columns. The report now auto-detects the PostgreSQL version and uses the appropriate query.
+- **26 previously failing Query Monitor specs** now pass — tests no longer depend on `Rails.cache` availability
+
+### Changed
+
+- **Dashboard UI redesign** — flattened the visual style to remove typical AI-generated patterns:
+  - Removed gradient buttons, gradient text on logo, backdrop blur on modals
+  - Removed `translateY` hover animations on cards and buttons
+  - Unified `border-radius` to 6px across all components (was 8–16px)
+  - Subdued box-shadows (`0 4px 16px` instead of `0 10px 40px`)
+  - Muted color palette — same CSS variables, lower saturation
+  - Background warmed from `#0f1114` to `#151719`
+  - Removed colored icon backgrounds from category cards
+  - Report links now transparent by default (tertiary fill on hover only)
+  - NEW badge restyled: tinted background instead of solid green
+  - Buttons use flat solid color instead of gradients
+- "Download" button renamed to "Export" with AI Prompt option added to the dropdown
+- New reports tagged with `NEW` badge in the dashboard sidebar
+- Query Monitor `enabled` and `session_id` public methods now return local state instead of hitting cache on every call
+
 ## [0.5.4] - 2026-02-11
 
 ### Fixed