This problem started with the recent update to rails. I also think it
may have to do with this statement
ActiveRecord::Base.connection_pool.clear_stale_cached_connections!
The postgres mailing list tells me these errors have to do with
threading in libpq.
On Wed, Nov 3, 2010 at 11:41 AM, Tim Uckun
<timuckun-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:> I am getting these types of errors quite frequently and am wondering
> what may be causing them or how to fix them.
>
> PGError: lost synchronization with server: got message type "T",
> length 1409286191
> PGError: lost synchronization with server: got message type "T",
> length 1409286191
> PGError: lost synchronization with server: got message type "T",
> length 1409286191
> PGError: lost synchronization with server: got message type "T",
> length 1409286191
> PGError: lost synchronization with server: got message type "T",
> length 1409286191
> PGError: lost synchronization with server: got message type "T",
> length 1409286191
> PGError: lost synchronization with server: got message type "e",
> length 980640103
> PGError: lost synchronization with server: got message type "e",
> length 980640103
> PGError: lost synchronization with server: got message type "e",
> length 980640103
>
>
> They tend to happen after the daemon is running for a while (a day or
> two). Needless to say once this happens the daemon is not working
> anymore.
>
> Any help in diagnosing and solving this problem would be much appreciated.
>
--
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.