Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 8F1D014E23D3 for ; Wed, 21 Dec 2011 12:09:39 -0400 (AST) Received: from gwmta.wicourts.gov ([165.219.244.99] helo=gw.wicourts.gov) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RdOjb-0000Yx-BK for pgsql-admin@postgresql.org; Wed, 21 Dec 2011 16:09:39 +0000 Received: from Courts-MTA by gw.wicourts.gov with Novell_GroupWise; Wed, 21 Dec 2011 10:09:26 -0600 Message-Id: <4EF1B04D0200002500043F4C@gw.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 8.0.1 Date: Wed, 21 Dec 2011 10:09:17 -0600 From: "Kevin Grittner" To: ,"Rural Hunter" Cc: "Jerry Sievers" , Subject: Re: lock problem References: <4EF18A8A0200002500043F0A@gw.wicourts.gov> <4EF1F027.507@gmail.com> <87aa6m7xqz.fsf@comcast.net> <4EF20333.8020404@gmail.com> In-Reply-To: <4EF20333.8020404@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Pg-Spam-Score: -6.8 (------) X-Archive-Number: 201112/113 X-Sequence-Number: 38871 Rural Hunter wrote: > I still have this question: > same statement A,B,C,D update same row. The start order is > A->B->C-D. From what I've gotten, B/C/D got the lock before A. > Why did that happen? Did you do anything to prevent it from happening? If not, the OS scheduler is going to give time to one process or another in a fairly unpredictable way. -Kevin