Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 32C8F9FB30D for ; Thu, 26 Oct 2006 11:48:39 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 15955-05 for ; Thu, 26 Oct 2006 14:47:23 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from floppy.pyrenet.fr (floppy.pyrenet.fr [194.116.145.2]) by postgresql.org (Postfix) with ESMTP id C60049FB368 for ; Thu, 26 Oct 2006 11:47:22 -0300 (ADT) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id 9683730E1C; Thu, 26 Oct 2006 16:47:20 +0200 (MET DST) From: "Carlo Stonebanks" X-Newsgroups: pgsql.performance Subject: Re: commit so slow program looks frozen Date: Thu, 26 Oct 2006 10:48:00 -0400 Organization: Hub.Org Networking Services Lines: 32 Message-ID: References: <6E0907A94904D94B99D7F387E08C4F570192F2D0@FALCON.INSIGHT> X-Complaints-To: usenet@news.hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2869 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 To: pgsql-performance@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200610/549 X-Sequence-Number: 21678 This is pretty interesting - where can I read more on this? Windows isn't actually hanging, one single command line window is - from its behaviour, it looks like the TCL postgresql package is waiting for pg_exec to come back from the commit (I believe the commit has actually gone through). It could even be that there's something wrong with the TCL package, but from my understanding it is one of the most complete interfaces out there - which is weird, because TCL seems to be the most unpopular language in the community. Caro ""Rocco Altier"" wrote in message news:6E0907A94904D94B99D7F387E08C4F570192F2D0@FALCON.INSIGHT... >I seem to remember Oleg/Teodor recently reporting a problem with Windows > hanging on a multi-processor machine, during a heavy load operation. > > In their case it seemed like a vacuum would allow it to wake up. They > did commit a patch that did not make it into the last minor version for > lack of testing. > > Perhaps you could see if that patch might work for you, which would also > help ease the argument against the patches lack of testing. > > -rocco > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend >