From beb5a8b11d28abe1a5202768aff3d56f5dcd716c Mon Sep 17 00:00:00 2001 From: pawurb Date: Tue, 3 Sep 2024 11:15:47 +0200 Subject: [PATCH] Update readme --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index f3a662d..b29768c 100644 --- a/README.md +++ b/README.md @@ -2,6 +2,8 @@ This gem allows to observe database locks generated by a Rails application. By default, locks data is not persisted anywhere in the PostgreSQL logs, so the only way to monitor it is via analyzing the transient state of the `pg_locks` metadata table. `pg-locks-monitor` is a simple tool that makes this process quick to implement and adjust to each app's individual requirements. +You can read [this blogpost](https://pawelurbanek.com/rails-postgresql-locks) for more detailed info on database locks in the Rails apps. + ## Usage `PgLocksMonitor` class provides a `snapshot!` method, which notifies selected channels about database locks that match configured criteria. @@ -136,8 +138,6 @@ Here's a sample lock notification: }, ``` -You can read [this blogpost](https://pawelurbanek.com/rails-postgresql-locks) for more detailed info on locks in the Rails apps. - ## Background job config This gem is intended to be used via a recurring background job, but it is agnostic to the background job provider. Here's a sample Sidekiq implementation: