Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 851E49FB73A; Mon, 12 Feb 2007 13:48:59 -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 10099-01-9; Mon, 12 Feb 2007 13:48:53 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 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 335059FB724; Mon, 12 Feb 2007 13:48:10 -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 17:48:08 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 12 Feb 2007 11:48:08 -0600 Subject: Re: Deadlock on transaction From: Scott Marlowe To: Ezequias Rodrigues da Rocha Cc: pgsql-sql@postgresql.org, pgsql-admin@postgresql.org In-Reply-To: <55c095e90702120943v2909044eo91445b0eda3958c7@mail.gmail.com> References: <55c095e90702120943v2909044eo91445b0eda3958c7@mail.gmail.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1171302488.3565.15.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Mon, 12 Feb 2007 11:48:08 -0600 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=BAYES_50, SPF_PASS, UNPARSEABLE_RELAY X-Spam-Level: X-Archive-Number: 200702/158 X-Sequence-Number: 24623 On Mon, 2007-02-12 at 11:43, Ezequias Rodrigues da Rocha wrote: > Hi list, > > I am curious becouse I am seen my postgresql locking the transactions > when i load a huge (in some case not to huge) numbers of records > 70,000 records. > > Could someone help me with it ? Are sure that what you're speaking of is a deadlock? Or is it just a stalled transaction while one one transaction waits for another to complete? A true deadlock means that two transactions are stalled waiting for the other to complete, and neither ever can complete, and they are DEADlocked. If you've just got a problem where an update is stalling all the other transactions, then give us a test case / example code of what's happening. If you've got a real deadlock that postgresql isn't catching, that's a much more serious problem.