rails-pg-extras 1.0.0 → 1.2.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 9b6b163cd88218757306517d2a4c25bb13c200464d41fbb4bc8c82f9831b4879
-  data.tar.gz: e1de0a513ba7833332f62b052d565367844d92726de14bbac7dcd75a0d7358ed
+  metadata.gz: 96b32211012cd93252e2fd58f870713a4717f57eaed8071b6fd3c32aeac31264
+  data.tar.gz: e4001940a894b757284e650c50400357f3d01e2e0273841fdf243099e88a8042
 SHA512:
-  metadata.gz: c8763536e9e1ec169155f48cf962c977f095e94b203d3930d491bb997725d8ab044d3df115dc1aa5a8e97fd1afe2fa180c9ec5c9c5a1fa010655288d5a0f8ea1
-  data.tar.gz: ae3d6fbabded46a62bf7ca32b01efe8bb48273d27a31296a578f6ff338384626c810e2a0cc4c57076834b057e0b42e17601f030d74647eea0cb59cd50c4bc923
+  metadata.gz: 6ccc4603aa90aba0229aa0c2c7ac76c9377e90e8e8704a107d52588472b5c4e05b8d3aeb8acb7ba2a6ff4a5fc9003c17c797932c6baaa337270314fb70ff47db
+  data.tar.gz: c73c394b1d2c5692eafa973f0daf6751e6e72b33b7baba67d69bc7385a60d058ada88a1d6ff6e52812daab647b6e5109bacef1cb4fd1cea23049fe1a2f9ca2c0

data/README.md

@@ -4,17 +4,40 @@ Rails port of [Heroku PG Extras](https://github.com/heroku/heroku-pg-extras) wit
 
 Included rake tasks and Ruby methods can be used to obtain information about a Postgres instance, that may be useful when analyzing performance issues. This includes information about locks, index usage, buffer cache hit ratios and vacuum statistics. Ruby API enables developers to easily integrate the tool into e.g. automatic monitoring tasks.
 
-Not using Rails? Check out the core dependency [pure Ruby version](https://github.com/pawurb/ruby-pg-extras).
+You can check out this blog post for detailed step by step tutorial on how to [optimize PostgreSQL using PG Extras library](https://pawelurbanek.com/postgresql-fix-performance).
 
-### Installation
+Alternative versions:
+
+- Core dependency - [Ruby](https://github.com/pawurb/ruby-pg-extras)
+
+- [NodeJS](https://github.com/pawurb/node-postgres-extras)
+
+- [Elixir](https://github.com/pawurb/ecto_psql_extras)
+
+- [Python](https://github.com/pawurb/ecto_psql_extras)
+
+## Installation
 
 In your Gemfile
 
 ```ruby
-gem 'rails-pg-extras'
+gem "rails-pg-extras"
 ```
 
-### Usage
+Some of the queries (e.g., `calls` and `outliers`) require [pg_stat_statements](https://www.postgresql.org/docs/current/pgstatstatements.html) extension enabled.
+
+You can check if it is enabled in your database by running:
+
+```ruby
+RailsPGExtras.extensions
+```
+You should see the similar line in the output:
+
+```bash
+| pg_stat_statements  | 1.7  | 1.7 | track execution statistics of all SQL statements executed |
+```
+
+## Usage
 
 Each command can be used as a rake task, or a directly from the Ruby code.
 
@@ -53,9 +76,9 @@ RailsPGExtras.cache_hit(in_format: :raw) =>
  #<PG::Result:0x00007f75777f7328 status=PGRES_TUPLES_OK ntuples=2 nfields=2 cmd_tuples=2>
 ```
 
-### Available methods
+## Available methods
 
-#### `cache_hit`
+### `cache_hit`
 
 ```
 $ rake pg_extras:cache_hit
@@ -69,7 +92,7 @@ $ rake pg_extras:cache_hit
 
 This command provides information on the efficiency of the buffer cache, for both index reads (`index hit rate`) as well as table reads (`table hit rate`). A low buffer cache hit ratio can be a sign that the Postgres instance is too small for the workload.
 
-#### `index_cache_hit`
+### `index_cache_hit`
 
 ```
 
@@ -85,7 +108,7 @@ $ rake pg_extras:index_cache_hit
 
 The same as `cache_hit` with each table's indexes cache hit info displayed seperately.
 
-#### `table_cache_hit`
+### `table_cache_hit`
 
 ```
 
@@ -101,7 +124,7 @@ $ rake pg_extras:table_cache_hit
 
 The same as `cache_hit` with each table's cache hit info displayed seperately.
 
-#### `index_usage`
+### `index_usage`
 
 ```
 $ rake pg_extras:index_usage
@@ -243,12 +266,12 @@ $ rake pg_extras:table_size
 (truncated results for brevity)
 ```
 
-This command displays the size of each table in the database, in MB. It is calculated by using the system administration function `pg_table_size()`, which includes the size of the main data fork, free space map, visibility map and TOAST data.
+This command displays the size of each table and materialized view in the database, in MB. It is calculated by using the system administration function `pg_table_size()`, which includes the size of the main data fork, free space map, visibility map and TOAST data.
 
 ### `table_indexes_size`
 
 ```
-$ rake pg_extras:table-indexes-size
+$ rake pg_extras:table_indexes_size
 
                              table                             | indexes_size
 ---------------------------------------------------------------+--------------
@@ -260,7 +283,7 @@ $ rake pg_extras:table-indexes-size
 (truncated results for brevity)
 ```
 
-This command displays the total size of indexes for each table, in MB. It is calcualtes by using the system administration function `pg_indexes_size()`.
+This command displays the total size of indexes for each table and materialized view, in MB. It is calcualtes by using the system administration function `pg_indexes_size()`.
 
 ### `total_table_size`
 
@@ -277,7 +300,7 @@ $ rake pg_extras:total_table_size
 (truncated results for brevity)
 ```
 
-This command displays the total size of each table in the database, in MB. It is calculated by using the system administration function `pg_total_relation_size()`, which includes table size, total index size and TOAST data.
+This command displays the total size of each table and materialized view in the database, in MB. It is calculated by using the system administration function `pg_total_relation_size()`, which includes table size, total index size and TOAST data.
 
 ### `unused_indexes`
 
@@ -322,7 +345,7 @@ $ rake pg_extras:seq_scans
 
 This command displays the number of sequential scans recorded against all tables, descending by count of sequential scans. Tables that have very high numbers of sequential scans may be underindexed, and it may be worth investigating queries that read from these tables.
 
-### long_running_queries
+### `long_running_queries`
 
 ```
 $ rake pg_extras:long_running_queries
@@ -337,7 +360,7 @@ $ rake pg_extras:long_running_queries
 
 This command displays currently running queries, that have been running for longer than 5 minutes, descending by duration. Very long running queries can be a source of multiple issues, such as preventing DDL statements completing or vacuum being unable to update `relfrozenxid`.
 
-### records_rank
+### `records_rank`
 
 ```
 $ rake pg_extras:records_rank
@@ -355,7 +378,7 @@ $ rake pg_extras:records_rank
 
 This command displays an estimated count of rows per table, descending by estimated count. The estimated count is derived from `n_live_tup`, which is updated by vacuum operations. Due to the way `n_live_tup` is populated, sparse vs. dense pages can result in estimations that are significantly out from the real count of rows.
 
-### bloat
+### `bloat`
 
 ```
 $ rake pg_extras:bloat
@@ -372,7 +395,7 @@ $ rake pg_extras:bloat
 
 This command displays an estimation of table "bloat" – space allocated to a relation that is full of dead tuples, that has yet to be reclaimed. Tables that have a high bloat ratio, typically 10 or greater, should be investigated to see if vacuuming is aggressive enough, and can be a sign of high table churn.
 
-### vacuum_stats
+### `vacuum_stats`
 
 ```
 $ rake pg_extras:vacuum_stats
@@ -388,20 +411,30 @@ $ rake pg_extras:vacuum_stats
 
 This command displays statistics related to vacuum operations for each table, including an estiamtion of dead rows, last autovacuum and the current autovacuum threshold. This command can be useful when determining if current vacuum thresholds require adjustments, and to determine when the table was last vacuumed.
 
-### mandelbrot
+### `kill_all`
+
+```ruby
+
+RailsPGExtras.kill_all
 
-```
-$ rake pg_extras:mandelbrot
 ```
 
-This command outputs the Mandelbrot set, calculated through SQL.
+This commands kills all the currently active connections to the database. It can be useful as a last resort when your database is stuck in a deadlock.
+
+### `extensions`
 
-## FAQ
+```ruby
 
-* Does is not violate the Heroku PG Extras license?
+RailsPGExtras.extensions
 
-The original plugin is MIT based so it means that copying and redistribution in any format is permitted.
+```
 
-## Disclaimer
+This command lists all the currently installed and available PostgreSQL extensions.
 
-This tool is in beta state.
+### mandelbrot
+
+```
+$ rake pg_extras:mandelbrot
+```
+
+This command outputs the Mandelbrot set, calculated through SQL.

data/lib/rails-pg-extras/version.rb

@@ -1,3 +1,5 @@
+# frozen_string_literal: true
+
 module RailsPGExtras
-  VERSION = "1.0.0"
+  VERSION = "1.2.3"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: rails-pg-extras
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.2.3
 platform: ruby
 authors:
 - pawurb
-autorequire: 
+autorequire:
 bindir: bin
 cert_chain: []
-date: 2020-01-18 00:00:00.000000000 Z
+date: 2020-10-08 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: 1.0.0
+        version: 1.2.3
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 1.0.0
+        version: 1.2.3
 - !ruby/object:Gem::Dependency
   name: activerecord
   requirement: !ruby/object:Gem::Requirement
@@ -93,7 +93,7 @@ homepage: http://github.com/pawurb/rails-pg-extras
 licenses:
 - MIT
 metadata: {}
-post_install_message: 
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -108,8 +108,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.0.6
-signing_key: 
+rubygems_version: 3.1.2
+signing_key:
 specification_version: 4
 summary: Rails PostgreSQL performance database insights
 test_files: