On Thu, Jul 30, 2009 at 10:27 AM, Csaba Nagy<nagy@xxxxxxxxxxxxxx> wrote: > > Sorry, I have to disagree here. If there's a spurious network error, you > have usually bigger problems. I prefer to have the connection killed > even if the network recovers I know this is a popular feeling. But you're throwing away decades of work in making TCP reliable. You would change feelings quickly if you ever faced this scenario too. All it takes is some bad memory or a bad wire and you would be turning a performance drain into random connection drops. > than risk an idle in transaction connection > to live forever when the client/network crashes for any reason. In case > of network failure the connection will probably be cleaned eventually, > but it did happen to me that a client machine crashed in the middle of a > transaction while not executing any SQL, and that connection stayed > until I killed it manually. Well it ought to have eventually died. Your patience may have ran out before the keep-alive timeouts fired though. -- greg http://mit.edu/~gsstark/resume.pdf -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
