In this case, the simplest solution is to not start the Ruby process until after the postgres process is accepting connections.
There are other hacks like sleeps or retries, but it's best to avoid the problem completely. -- 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.
