Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 4A2D59FB51A for ; Mon, 12 Feb 2007 15:56:36 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 80589-03 for ; Mon, 12 Feb 2007 15:56:29 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id 661269FB638 for ; Mon, 12 Feb 2007 15:56:31 -0400 (AST) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Mon, 12 Feb 2007 19:56:30 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 12 Feb 2007 13:56:30 -0600 Subject: Re: [SQL] Deadlock on transaction From: Scott Marlowe To: Ezequias Rodrigues da Rocha Cc: Richard Huxton , pgsql-admin@postgresql.org In-Reply-To: <55c095e90702121120s5b98a2d8u4a05a31f9625ffa@mail.gmail.com> References: <55c095e90702120943v2909044eo91445b0eda3958c7@mail.gmail.com> <1171302488.3565.15.camel@state.g2switchworks.com> <55c095e90702121008u6d3d27c0m16e52d63f97c3e7d@mail.gmail.com> <45D0B565.9060402@archonet.com> <55c095e90702121047x1c66b098xbcf0d308195ff584@mail.gmail.com> <45D0B8A4.7000602@archonet.com> <55c095e90702121120s5b98a2d8u4a05a31f9625ffa@mail.gmail.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1171310190.3565.22.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Mon, 12 Feb 2007 13:56:30 -0600 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=AWL, BAYES_50, SPF_PASS, UNPARSEABLE_RELAY X-Spam-Level: X-Archive-Number: 200702/169 X-Sequence-Number: 24634 On Mon, 2007-02-12 at 13:20, Ezequias Rodrigues da Rocha wrote: > This is delphi. I don't intent you understand but the sql actions are > quite simple (I am reading a list of numbers). Hmmm. I'm not seeing anything in your example that should be blocking other transactions. Is there anything that Delphi is doing here that we don't see from your code? I.e. does to toss a "for update" on the ends of selects, or "lock table" in there we don't see? Maybe you could turn on logging of ALL queries in the database and see what's really going on there, cause I'm not seeing anything in your code to point to blocking.