The log size issue was due to advisory locks, which are no longer used, largely for that exact reason!
Advisory locks themselves are very lightweight, but they are owned by the connection that took the lock initially. When any other connection attempts to release the lock Postgres logs a big fat WARNING. This situation happens constantly because the connection checked out from the db pool is random—the larger the pool the less likely that the checked out connection owned the advisory lock.
The new system writes rows to an oban_beats table and operates warning free. Definitely upgrade to 0.8.0 if you haven’t already!
