From 30fb4a7cc9d11d2c1572d18cfe9a474a1a383c56 Mon Sep 17 00:00:00 2001 From: Isaac Kearse Date: Thu, 25 Apr 2024 17:14:39 +1200 Subject: [PATCH] Clarify PgBouncer workaround --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 045423075..2e295afaa 100644 --- a/README.md +++ b/README.md @@ -1383,7 +1383,7 @@ _Note: Rails `travel`/`travel_to` time helpers do not have millisecond precision GoodJob is not compatible with PgBouncer in _transaction_ mode, but is compatible with PgBouncer's _connection_ mode. GoodJob uses connection-based advisory locks and LISTEN/NOTIFY, both of which require full database connections. -A workaround to this limitation is to make a direct database connection available to GoodJob. With Rails 6.0's support for [multiple databases](https://guides.rubyonrails.org/active_record_multiple_databases.html), a direct connection to the database can be configured: +If you want to use PgBouncer with the rest of your Rails app you can workaround this limitation by making a direct database connection available to GoodJob. With Rails 6.0's support for [multiple databases](https://guides.rubyonrails.org/active_record_multiple_databases.html), a direct connection to the database can be configured by following the three steps below. 1. Define a direct connection to your database that is not proxied through PgBouncer, for example: