> > > > Any chance you could single-step through WaitLatchOrSocket() with a > > > debugger? Without additional information this is rather hard to > > > diagnose. > > > > > > > Uh I sure can, but I have no idea what to look for :) Anything > > specific? > > Things that'd be interesting: > 1) what are the arguments passed to WaitLatchOrSocket(), most > importantly wakeEvents and sock > 2) are we busy looping, or is WaitForMultipleObjects() blocking > endlessly > 3) If you kill -9 (well, terminate in the task manager) a client, while > stepping serverside in WaitLatchOrSocket, does > WaitForMultipleObjects() return? If so, what paths are we taking? >
The process definitely isn't busy looping - zero CPU usage. I'll try to set up debugging, it may take some time though (unfamiliar with PostgreSQL internals and Windows debugging techniques).
