Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id E2A3F9FA0C4 for ; Thu, 26 Oct 2006 14:49:30 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 79747-01 for ; Thu, 26 Oct 2006 14:49:23 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from floppy.pyrenet.fr (news.pyrenet.fr [194.116.145.2]) by postgresql.org (Postfix) with ESMTP id 2F7CE9FA19B for ; Thu, 26 Oct 2006 14:49:23 -0300 (ADT) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id 491CD30E1C; Thu, 26 Oct 2006 19:49:22 +0200 (MET DST) From: "Carlo Stonebanks" X-Newsgroups: pgsql.performance Subject: Re: commit so slow program looks frozen Date: Thu, 26 Oct 2006 13:49:57 -0400 Organization: Hub.Org Networking Services Lines: 18 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; Response 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.053 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200610/557 X-Sequence-Number: 21686 > when it happens, make sure to query pg_locks and see what is going on > there lock issues are not supposed to manifest on a commit, which > releases locks, but you never know. There aren't any pedning locks (assuming that pgAdmin is using pg_locks to display pendin glocks). > There have been reports of > insonsistent lock ups on windows (espeically multi-processor) which > you might be experiencing. Make sure you have the very latest version > of pg 8.1.x. Also consider checking out 8.2 and see if you can > reproduce the behavior there...this will require compiling postgresql. Are these associated with any type of CPU? Carlo