title: PG::Error EOF detected on Heroku Cedar, rails 3.2.11
body: <p>Having experienced a few periods of downtime, we've recently upgraded to a production environment in Heroku (Crane database plus 2 x web dynos) however we've seen no improvement. In fact reliability seems to have decreased since upgrading.</p>
  
  <p>The root cause seems to be the following exception:
   PG::Error (SSL SYSCALL error: EOF detected
  which causes the dyno to fail and - eventually - restart, but not before causing some downtime.</p>
  
  <p>I've no idea what's causing it. Common culprits appear to be Resque and Unicorn, neither of which I'm using. We're on rails 3.2.11, on Heroku Cedar, using pg gem 1.14.1</p>
  
  <p>Logs report the following at crash time:</p>
  
  <pre><code>    2013-05-23T19:01:33+00:00 app[heroku-postgres]: source=HEROKU_POSTGRESQL_PINK measure.current_transaction=34490 measure.db_size=38311032bytes measure.tables=19 measure.active-connections=7 measure.waiting-connections=0 measure.index-cache-hit-rate=0.99438 measure.table-cache-hit-rate=0.8824     
  2013-05-23T19:01:35.123633+00:00 app[web.2]: 
  2013-05-23T19:01:35.123633+00:00 app[web.2]: PG::Error (SSL SYSCALL error: EOF detected
  2013-05-23T19:01:35.123633+00:00 app[web.2]: ):
  </code></pre>
  
  <p>I have read the following: <a href="https://groups.google.com/forum/?fromgroups#!topic/heroku/a6iviwAFgdY" rel="nofollow">https://groups.google.com/forum/?fromgroups#!topic/heroku/a6iviwAFgdY</a> but can't find anything that might help.</p>