Yes, I am familiar with all the Heroku docs. That document covers Resque and Unicorn, whereas my problem at this time is with Puma.
I have a dozen other Apps all working with the same setup and no worker PG connection errors... but this newer App is problematic. Hence my original question. This is most frustrating as I have nothing but good previous examples I am working from, with this one being the odd one out. On Friday, January 19, 2018 at 2:08:21 PM UTC-5, Michael Granger wrote: > > On Friday, January 19, 2018 at 10:54:05 AM UTC-8, David Lazar wrote: >> >> >> I am seeing this in a heroku worker. The first time the worker does a >> job, it works. The second time, this error is thrown. So the solution is >> what? To add to the worker_on_boot in Puma config and establish a >> connection? >> > > Sorry, I'm not very familiar with Heroku, but this document covers what I > was suggesting: > https://devcenter.heroku.com/articles/forked-pg-connections > -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
