It seems to be what occurred : the windows client crashed ... Still, it's a bit of a problem to have a filesystem full in a matter of minutes just because a client machine crashed while having an SSL connection opened on the postgresql server... On Thursday 29 March 2007 19:40:18 Peter Koczan wrote: > I saw this on one of my servers a few weeks ago (it was running > postgres 7.4under linux, and I believe the users in question were just > running psql). I > talked to someone more knowledgeable about SSL about this, and he said that > these errors are usually due to some abrupt disconnection somewhere (in any > application, not just postgres). My best guess is that the connection was > broken while data was trying to be fed, causing the server to say "Hey, > where'd you go?...Here's your data again...Hey where'd you go?..." ad > infinitum. > > Other than that, I have no idea what would cause this or how to fix it > short of restarting the postgres server or rebooting the machine. > > That being said, I don't know a whole lot about SSL, and people with more > knowledge are more than welcome to weigh in. > > Peter >
