On Nov 9, 2007 4:36 PM, Tena Sakai <tsakai@xxxxxxxxxxxxxx> wrote: > Hi Scott, > > > > Most likely what is happening is that you have a firewall between your > > app and your db server that is closing idle connections after x minutes. > > Thanks for your comment. > > I hate to be disagreeable, but the app and postgres are running > on the same computer. The app is a java program using jdbc to > issue postgres commands. However, I see the same message via > psql (on the same machine). Hmmm. Well, when you see an error like unexpected EOF on client connection then that means that the client "disappeared" without closing the connection, or the network connection went away. Either way, the pgsql backend was still alive, and tried to send something to the client, and the client wasn't there. I.e. the problem isn't generally a postgresql problem, it's a client problem. So, the more info about the client app the better chance of fixing it. Note that if you've got a lot of "idle in transactions" connections, that's a bad thing because it prevents postgresql from being properly vacuumed. Most connection managers can be set to NOT issue a begin as part of a connection reset when returning it to the pool. ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
