rails-pg-extras 1.0.0 → 1.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 9b6b163cd88218757306517d2a4c25bb13c200464d41fbb4bc8c82f9831b4879
-  data.tar.gz: e1de0a513ba7833332f62b052d565367844d92726de14bbac7dcd75a0d7358ed
+  metadata.gz: 780e5bd6ea4fb796ff83e4e249ac603ae7a74bf4a11d6e7414a72f82a433926c
+  data.tar.gz: 3499bfe705e3bcde82fa4b6417cbd275d3c9cbea6f57b03db384a3b370323020
 SHA512:
-  metadata.gz: c8763536e9e1ec169155f48cf962c977f095e94b203d3930d491bb997725d8ab044d3df115dc1aa5a8e97fd1afe2fa180c9ec5c9c5a1fa010655288d5a0f8ea1
-  data.tar.gz: ae3d6fbabded46a62bf7ca32b01efe8bb48273d27a31296a578f6ff338384626c810e2a0cc4c57076834b057e0b42e17601f030d74647eea0cb59cd50c4bc923
+  metadata.gz: a790f7359529dc48fce3ae4632742565a0de41b4d9463c419a1cd676361a40fed66f26e84e0d19611f466b533f67927813747a05d5e2d517b348e6be04bc5843
+  data.tar.gz: 5bb4bf5375df56cb3a48338e6e785cc9dd11d9859ab7c6290e5367c84b390f8c4433131920854f8fcc188df20f1bf55542c807d15a3bb3eee32d62a9888ec652

data/README.md

@@ -6,15 +6,15 @@ Included rake tasks and Ruby methods can be used to obtain information about a P
 
 Not using Rails? Check out the core dependency [pure Ruby version](https://github.com/pawurb/ruby-pg-extras).
 
-### Installation
+## Installation
 
 In your Gemfile
 
 ```ruby
-gem 'rails-pg-extras'
+gem "rails-pg-extras"
 ```
 
-### Usage
+## Usage
 
 Each command can be used as a rake task, or a directly from the Ruby code.
 
@@ -53,9 +53,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 +69,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 +85,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 +101,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
@@ -322,7 +322,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 +337,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 +355,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 +372,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,6 +388,16 @@ $ 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.
 
+### `kill_all`
+
+```ruby
+
+RailsPGExtras.kill_all
+
+```
+
+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.
+
 ### mandelbrot
 
 ```
@@ -401,7 +411,3 @@ This command outputs the Mandelbrot set, calculated through SQL.
 * Does is not violate the Heroku PG Extras license?
 
 The original plugin is MIT based so it means that copying and redistribution in any format is permitted.
-
-## Disclaimer
-
-This tool is in beta state.

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

@@ -1,3 +1,3 @@
 module RailsPGExtras
-  VERSION = "1.0.0"
+  VERSION = "1.1.0"
 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.1.0
 platform: ruby
 authors:
 - pawurb
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2020-01-18 00:00:00.000000000 Z
+date: 2020-02-23 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.1.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 1.0.0
+        version: 1.1.0
 - !ruby/object:Gem::Dependency
   name: activerecord
   requirement: !ruby/object:Gem::Requirement