rails-pg-extras 1.4.0 → 1.6.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3306ddaeabad3f9e9b82a97fe044121a1df8924e092b6087625a606af0c198df
-  data.tar.gz: 1ab601c34fbe458a9e0b09de4c15b1405fe5d3aa77f9cafd0dd3c37472f39af2
+  metadata.gz: b44baf89a4349ef720b371a8a83a8397e0e848794b1bf248398cfd19c5f606d5
+  data.tar.gz: ebdabe9d275ed5ef7132ce604f894a42520226db0b1dc5d50acd092a0aed6dd4
 SHA512:
-  metadata.gz: 298c4fd79dc18eab15c1c9e05e7676f5533d686052e4b189cf5da4f53b524b85d68fa4a4ef0c694d026fdaabe72fa28b1a0bee4507bde510c97b8f6a2bf877df
-  data.tar.gz: 543fd9fe51a0f9143a3202639c91405f9669fe721c8946c5598e0e9655ba13ecec1d8ce93b50587f005c3323e050839e85fd30a337ddf3b7106ebc017b263a79
+  metadata.gz: d0b9e1505835974df1959e620385461f7c5c92838efadd18abb57a5656d1b942d8f097f7c70389e815a96a5dcb239b67b16cee430188e0532ccef57eb2a6ff50
+  data.tar.gz: 269a9b8bb29c5114c43885d61f849b3ed73664cb7c5e9e772c85281cacebbce641b224fe0e246bda5a7ab5426210ee3a75a0ac0a36c6555abb64988d7b66b733

data/README.md

@@ -89,7 +89,9 @@ RailsPGExtras.long_running_queries(args: { threshold: "200 milliseconds" })
 
 ### `cache_hit`
 
-```
+```ruby
+RailsPGExtras.cache_hit
+
 $ rake pg_extras:cache_hit
 
       name      |         ratio
@@ -101,9 +103,13 @@ $ 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.
 
+[More info](https://pawelurbanek.com/postgresql-fix-performance#cache-hit)
+
 ### `index_cache_hit`
 
-```
+```ruby
+
+RailsPGExtras.index_cache_hit
 
 $ rake pg_extras:index_cache_hit
 
@@ -117,9 +123,13 @@ $ rake pg_extras:index_cache_hit
 
 The same as `cache_hit` with each table's indexes cache hit info displayed separately.
 
+[More info](https://pawelurbanek.com/postgresql-fix-performance#cache-hit)
+
 ### `table_cache_hit`
 
-```
+```ruby
+
+RailsPGExtras.table_cache_hit
 
 $ rake pg_extras:table_cache_hit
 
@@ -133,9 +143,35 @@ $ rake pg_extras:table_cache_hit
 
 The same as `cache_hit` with each table's cache hit info displayed seperately.
 
-### `index_usage`
+[More info](https://pawelurbanek.com/postgresql-fix-performance#cache-hit)
+
+### `db_settings`
+
+```ruby
+
+RailsPGExtras.db_settings
+
+$ rake pg_extras:db_settings
+
+             name             | setting | unit |
+------------------------------+---------+------+
+ checkpoint_completion_target | 0.7     |      |
+ default_statistics_target    | 100     |      |
+ effective_cache_size         | 1350000 | 8kB  |
+ effective_io_concurrency     | 1       |      |
+(truncated results for brevity)
 
 ```
+
+This method displays values for selected PostgreSQL settings. You can compare them with settings recommended by [PGTune](https://pgtune.leopard.in.ua/#/) and tweak values to improve performance.
+
+[More info](https://pawelurbanek.com/postgresql-fix-performance#cache-hit)
+
+### `index_usage`
+
+```ruby
+RailsPGExtras.index_usage
+
 $ rake pg_extras:index_usage
 
        relname       | percent_of_times_index_used | rows_in_table
@@ -152,7 +188,9 @@ This command provides information on the efficiency of indexes, represented as w
 
 ### `locks`
 
-```
+```ruby
+RailsPGExtras.locks
+
 $ rake pg_extras:locks
 
  procpid | relname | transactionid | granted |     query_snippet     | mode             |       age
@@ -168,9 +206,13 @@ $ rake pg_extras:locks
 
 This command displays queries that have taken out an exclusive lock on a relation. Exclusive locks typically prevent other operations on that relation from taking place, and can be a cause of "hung" queries that are waiting for a lock to be granted.
 
+[More info](https://pawelurbanek.com/postgresql-fix-performance#deadlocks)
+
 ### `all_locks`
 
-```
+```ruby
+RailsPGExtras.all_locks
+
 $ rake pg_extras:all_locks
 ```
 
@@ -178,7 +220,9 @@ This command displays all the current locks, regardless of their type.
 
 ### `outliers`
 
-```
+```ruby
+RailsPGExtras.outliers(args: { limit: 20 })
+
 $ rake pg_extras:outliers
 
                    qry                   |    exec_time     | prop_exec_time |   ncalls    | sync_io_time
@@ -196,9 +240,13 @@ This command displays statements, obtained from `pg_stat_statements`, ordered by
 
 Typically, an efficient query will have an appropriate ratio of calls to total execution time, with as little time spent on I/O as possible. Queries that have a high total execution time but low call count should be investigated to improve their performance. Queries that have a high proportion of execution time being spent on synchronous I/O should also be investigated.
 
+[More info](https://pawelurbanek.com/postgresql-fix-performance#missing-indexes)
+
 ### `calls`
 
-```
+```ruby
+RailsPGExtras.calls(args: { limit: 10 })
+
 $ rake pg_extras:calls
 
                    qry                   |    exec_time     | prop_exec_time |   ncalls    | sync_io_time
@@ -213,9 +261,13 @@ $ rake pg_extras:calls
 
 This command is much like `pg:outliers`, but ordered by the number of times a statement has been called.
 
+[More info](https://pawelurbanek.com/postgresql-fix-performance#missing-indexes)
+
 ### `blocking`
 
-```
+```ruby
+RailsPGExtras.blocking
+
 $ rake pg_extras:blocking
 
  blocked_pid |    blocking_statement    | blocking_duration | blocking_pid |                                        blocked_statement                           | blocked_duration
@@ -226,9 +278,13 @@ $ rake pg_extras:blocking
 
 This command displays statements that are currently holding locks that other statements are waiting to be released. This can be used in conjunction with `pg:locks` to determine which statements need to be terminated in order to resolve lock contention.
 
-#### `total_index_size`
+[More info](https://pawelurbanek.com/postgresql-fix-performance#deadlocks)
+
+### `total_index_size`
+
+```ruby
+RailsPGExtras.total_index_size
 
-```
 $ rake pg_extras:total_index_size
 
   size
@@ -241,7 +297,9 @@ This command displays the total size of all indexes on the database, in MB. It i
 
 ### `index_size`
 
-```
+```ruby
+RailsPGExtras.index_size
+
 $ rake pg_extras:index_size
                              name                              |  size
 ---------------------------------------------------------------+---------
@@ -262,7 +320,9 @@ This command displays the size of each each index in the database, in MB. It is
 
 ### `table_size`
 
-```
+```ruby
+RailsPGExtras.table_size
+
 $ rake pg_extras:table_size
 
                              name                              |  size
@@ -279,7 +339,9 @@ This command displays the size of each table and materialized view in the databa
 
 ### `table_indexes_size`
 
-```
+```ruby
+RailsPGExtras.table_indexes_size
+
 $ rake pg_extras:table_indexes_size
 
                              table                             | indexes_size
@@ -296,7 +358,9 @@ This command displays the total size of indexes for each table and materialized
 
 ### `total_table_size`
 
-```
+```ruby
+RailsPGExtras.total_table_size
+
 $ rake pg_extras:total_table_size
 
                              name                              |  size
@@ -313,7 +377,9 @@ This command displays the total size of each table and materialized view in the
 
 ### `unused_indexes`
 
-```
+```ruby
+RailsPGExtras.unused_indexes(args: { min_scans: 20 })
+
 $ rake pg_extras:unused_indexes
 
           table      |                       index                | index_size | index_scans
@@ -326,9 +392,33 @@ $ rake pg_extras:unused_indexes
 
 This command displays indexes that have < 50 scans recorded against them, and are greater than 5 pages in size, ordered by size relative to the number of index scans. This command is generally useful for eliminating indexes that are unused, which can impact write performance, as well as read performance should they occupy space in memory.
 
-### `seq_scans`
+[More info](https://pawelurbanek.com/postgresql-fix-performance#unused-indexes)
+
+### `null_indexes`
+
+```ruby
+
+RailsPGExtras.null_indexes(args: { min_relation_size_mb: 10 })
+
+$ rake pg_extras:null_indexes
+
+   oid   |         index      | index_size | unique | indexed_column | null_frac | expected_saving
+---------+--------------------+------------+--------+----------------+-----------+-----------------
+  183764 | users_reset_token  | 1445 MB    | t      | reset_token    |   97.00%  | 1401 MB
+   88732 | plan_cancelled_at  | 539 MB     | f      | cancelled_at   |    8.30%  | 44 MB
+ 9827345 | users_email        | 18 MB      | t      | email          |   28.67%  | 5160 kB
 
 ```
+
+This command displays indexes that contain `NULL` values. A high ratio of `NULL` values means that using a partial index excluding them will be beneficial in case they are not used for searching.
+
+[More info](https://pawelurbanek.com/postgresql-fix-performance#null-indexes)
+
+### `seq_scans`
+
+```ruby
+RailsPGExtras.seq_scans
+
 $ rake pg_extras:seq_scans
 
                name                |  count
@@ -341,22 +431,18 @@ $ rake pg_extras:seq_scans
  messages                          |  3922247
  contests_customers                |  2915972
  classroom_goals                   |  2142014
- contests                          |  1370267
- goals                             |  1112659
- districts                         |   158995
- rollup_reports                    |   115942
- customers                         |    93847
- schools                           |    92984
- classrooms                        |    92982
- customer_settings                 |    91226
 (truncated results for brevity)
 ```
 
 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 under-indexed, and it may be worth investigating queries that read from these tables.
 
+[More info](https://pawelurbanek.com/postgresql-fix-performance#missing-indexes)
+
 ### `long_running_queries`
 
-```
+```ruby
+RailsPGExtras.long_running_queries(args: { threshold: "200 milliseconds" })
+
 $ rake pg_extras:long_running_queries
 
   pid  |    duration     |                                      query
@@ -371,7 +457,9 @@ This command displays currently running queries, that have been running for long
 
 ### `records_rank`
 
-```
+```ruby
+RailsPGExtras.records_rank
+
 $ rake pg_extras:records_rank
 
                name                | estimated_count
@@ -389,7 +477,9 @@ This command displays an estimated count of rows per table, descending by estima
 
 ### `bloat`
 
-```
+```ruby
+RailsPGExtras.bloat
+
 $ rake pg_extras:bloat
 
  type  | schemaname |           object_name         | bloat |   waste
@@ -404,9 +494,13 @@ $ 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.
 
+[More info](https://pawelurbanek.com/postgresql-fix-performance#bloat)
+
 ### `vacuum_stats`
 
-```
+```ruby
+RailsPGExtras.vacuum_stats
+
 $ rake pg_extras:vacuum_stats
 
  schema |         table         | last_vacuum | last_autovacuum  |    rowcount    | dead_rowcount  | autovacuum_threshold | expect_autovacuum
@@ -430,20 +524,49 @@ 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.
 
+### `buffercache_stats`
+
+This command shows the relations buffered in database share buffer, ordered by percentage taken. It also shows that how much of the whole relation is buffered.
+
+```ruby
+RailsPGExtras.buffercache_stats(args: { limit: 10 })
+```
+
+### `buffercache_usage`
+
+This command calculates how many blocks from which table are currently cached.
+
+```ruby
+RailsPGExtras.buffercache_usage(args: { limit: 20 })
+```
+
 ### `extensions`
 
 ```ruby
 
 RailsPGExtras.extensions
 
+$ rake pg_extras:extensions
+
+| pg_stat_statements | 1.7 | 1.7 | track execution statistics of all SQL statements executed
+ (truncated results for brevity)
+
 ```
 
 This command lists all the currently installed and available PostgreSQL extensions.
 
 ### mandelbrot
 
-```
+```ruby
+RailsPGExtras.mandelbrot
+
 $ rake pg_extras:mandelbrot
 ```
 
 This command outputs the Mandelbrot set, calculated through SQL.
+
+## Query sources
+
+- [https://github.com/heroku/heroku-pg-extras](https://github.com/heroku/heroku-pg-extras)
+- [https://hakibenita.com/postgresql-unused-index-size](https://hakibenita.com/postgresql-unused-index-size)
+- [https://sites.google.com/site/itmyshare/database-tips-and-examples/postgres/useful-sqls-to-check-contents-of-postgresql-shared_buffer](https://sites.google.com/site/itmyshare/database-tips-and-examples/postgres/useful-sqls-to-check-contents-of-postgresql-shared_buffer)

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

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module RailsPGExtras
-  VERSION = "1.4.0"
+  VERSION = "1.6.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: rails-pg-extras
 version: !ruby/object:Gem::Version
-  version: 1.4.0
+  version: 1.6.0
 platform: ruby
 authors:
 - pawurb
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2021-01-26 00:00:00.000000000 Z
+date: 2021-04-05 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.4.0
+        version: 1.6.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 1.4.0
+        version: 1.6.0
 - !ruby/object:Gem::Dependency
   name: activerecord
   requirement: !ruby/object:Gem::Requirement