rails-pg-extras 5.2.1 → 5.2.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4bd83f21b85de2b816dc334b72ad1bd0dfcb0f13ea6946fec42ebb93f47ba876
-  data.tar.gz: 4e9e5b00cc7e07cf3baa1bc3e224fe8ab50510afa909b47e753873fb1e7a11e7
+  metadata.gz: 831f887d91a8519dc968d3f612eb08059100e99d717db2a8ce6f0c13684d4714
+  data.tar.gz: f8da112789be789c8f1be7c7e11b27c94c5e8166e7096381cdfa726140fb3df4
 SHA512:
-  metadata.gz: 1a30823d47f9e0cab719b7ee6e750da28c751f4dc20d21756f7f3a633c07dd6390397e09502300cfcf9185184a9e00af83de40f2fd9b12a6319a6ade31ccb26f
-  data.tar.gz: f01d58920638949122f26a74857cdab232168b274aee2d28d180eed09ea60a48ace036aa3ba772dc8ce41893d6e4a4397255167bc5ccf699a181c7205438ed93
+  metadata.gz: 152d6244f1e32d32c3f98510b7316b224cc22c9e3a40ea84ce130e109335adf222f3e43391285dfd3e8c8ab51285a0b0933fe9529fabc2c4344ab2831b08bcbf
+  data.tar.gz: 51d26d67deaa392f3c8055f55cf6c0ac0e54dfa284eaf9445b59cb49ad14b7a47a0f2e0e057858bde2a1bace4309bd6aa17389b5804b8daf2cd0dba8e3506683

data/README.md

@@ -51,7 +51,7 @@ You should see the similar line in the output:
 RailsPgExtras.add_extensions
 ```
 
-By deafult a primary ActiveRecord database connection is used for running metadata queries, rake tasks and web UI. To connect to a different database you can specify an `ENV['RAILS_PG_EXTRAS_DATABASE_URL']` value in the following format:
+By default a primary ActiveRecord database connection is used for running metadata queries, rake tasks and web UI. To connect to a different database you can specify an `ENV['RAILS_PG_EXTRAS_DATABASE_URL']` value in the following format:
 
 ```ruby
 ENV["RAILS_PG_EXTRAS_DATABASE_URL"] = "postgresql://postgres:secret@localhost:5432/database_name"
@@ -152,18 +152,18 @@ RailsPgExtras.measure_queries { User.limit(10).map(&:team) }
  :queries=>
   {"SELECT \"users\".* FROM \"users\" LIMIT $1"=>
     {:count=>1,
-     :total_duration=>3.452000004472211,
-     :min_duration=>3.452000004472211,
-     :max_duration=>3.452000004472211,
-     :avg_duration=>3.452000004472211},
+     :total_duration=>1.9,
+     :min_duration=>1.9,
+     :max_duration=>1.9,
+     :avg_duration=>1.9},
    "SELECT \"teams\".* FROM \"teams\" WHERE \"teams\".\"id\" = $1 LIMIT $2"=>
     {:count=>10,
-     :total_duration=>14.487000000372063,
-     :min_duration=>0.778000001446344,
-     :max_duration=>1.985000002605375,
-     :avg_duration=>1.4487000000372063}},
- :total_duration=>24.812000003294088,
- :sql_duration=>17.939000004844274}
+     :total_duration=>0.94,
+     :min_duration=>0.62,
+     :max_duration=>1.37,
+     :avg_duration=>0.94}},
+ :total_duration=>13.35,
+ :sql_duration=>11.34}
 
 RailsPgExtras.measure_queries { User.limit(10).includes(:team).map(&:team) }
 
@@ -171,21 +171,36 @@ RailsPgExtras.measure_queries { User.limit(10).includes(:team).map(&:team) }
  :queries=>
   {"SELECT \"users\".* FROM \"users\" LIMIT $1"=>
     {:count=>1,
-     :total_duration=>3.7079999965499155,
-     :min_duration=>3.7079999965499155,
-     :max_duration=>3.7079999965499155,
-     :avg_duration=>3.7079999965499155},
+     :total_duration=>3.43,
+     :min_duration=>3.43,
+     :max_duration=>3.43,
+    :avg_duration=>3.43},
    "SELECT \"teams\".* FROM \"teams\" WHERE \"teams\".\"id\" IN ($1, $2, $3, $4, $5, $6, $7, $8)"=>
     {:count=>1,
-     :total_duration=>2.422000005026348,
-     :min_duration=>2.422000005026348,
-     :max_duration=>2.422000005026348,
-     :avg_duration=>2.422000005026348}},
- :total_duration=>9.905999999318738,
- :sql_duration=>6.1300000015762635}
+     :total_duration=>2.59,
+     :min_duration=>2.59,
+     :max_duration=>2.59,
+     :avg_duration=>2.59}},
+ :total_duration=>9.75,
+ :sql_duration=>6.02}
 
 ```
 
+Optionally, by including [Marginalia gem](https://github.com/basecamp/marginalia) and configuring it to display query backtraces:
+
+`config/development.rb`
+
+```ruby
+
+Marginalia::Comment.components = [:line]
+
+```
+
+you can add this info to the output:
+
+![Marginalia logs](https://github.com/pawurb/rails-pg-extras/raw/master/marginalia-logs.png)
+
+
 ### `table_info`
 
 This method displays metadata metrics for all or a selected table. You can use it to check the table's size, its cache hit metrics, and whether it is correctly indexed. Many sequential scans or no index scans are potential indicators of misconfigured indexes. This method aggregates data provided by other methods in an easy to analyze summary format.

data/lib/rails_pg_extras/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module RailsPgExtras
-  VERSION = "5.2.1"
+  VERSION = "5.2.2"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: rails-pg-extras
 version: !ruby/object:Gem::Version
-  version: 5.2.1
+  version: 5.2.2
 platform: ruby
 authors:
 - pawurb
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2023-03-01 00:00:00.000000000 Z
+date: 2023-04-09 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: ruby-pg-extras
@@ -16,14 +16,14 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 5.2.1
+        version: 5.2.2
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 5.2.1
+        version: 5.2.2
 - !ruby/object:Gem::Dependency
   name: rails
   requirement: !ruby/object:Gem::Requirement
@@ -106,6 +106,7 @@ files:
 - lib/rails_pg_extras/version.rb
 - lib/rails_pg_extras/web.rb
 - lib/rails_pg_extras/web/engine.rb
+- marginalia-logs.png
 - pg-extras-ui.png
 - rails-pg-extras-diagnose.png
 - rails-pg-extras.gemspec