X-Original-To: pgsql-sql@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id CD9DA474E4F for ; Tue, 25 Feb 2003 20:05:34 -0500 (EST) Received: from postgresql.org ([64.49.215.8]) by localhost (postgresql.org [64.49.215.8:10024]) (amavisd-new) with SMTP id 39719-09 for ; Tue, 25 Feb 2003 20:05:24 -0500 (EST) Received: from h-e.com (wan-vc8fa2d.ston.biz.mindspring.com [216.135.168.77]) by postgresql.org (Postfix) with ESMTP id 68144475A4B for ; Tue, 25 Feb 2003 19:55:55 -0500 (EST) Received: from [192.168.42.42] (HELO h-e.com) by h-e.com (CommuniGate Pro SMTP 3.5.9) with ESMTP id 89744 for pgsql-sql@postgresql.org; Tue, 25 Feb 2003 16:55:57 -0800 Date: Tue, 25 Feb 2003 16:55:57 -0800 Mime-Version: 1.0 (Apple Message framework v551) Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: Postgres locking From: Bob Smith To: pgsql-sql Content-Transfer-Encoding: 7bit Message-Id: <10995E4C-4925-11D7-8FCC-0003933DD370@h-e.com> X-Mailer: Apple Mail (2.551) X-Virus-Scanned: by amavisd-new X-Archive-Number: 200302/569 X-Sequence-Number: 11967 I'm trying to use select for update locks in Postgres. When I do this: begin work; select data from table where key = 1 for update; in two psql's running simultaneously, about half the time the second transaction blocks and waits for the first to end (which is what I want it to do), the other half the time I get this: ERROR: XactLockTableWait: LockAcquire failed and the transaction is aborted. I can't find any pattern, if I do the same statements in the same order several times, it will be block one time and error the next apparently at random. I also tried using LOCK TABLE and found the same basic problem, sometimes the second transaction will block, other times it will abort with: ERROR: LockRelation: LockAcquire failed Do I have a configuration problem? Is this a bug in Postgres? I'm still running 7.2.1, would upgrading to 7.3 fix this? Thanks! Bob Smith Hammett & Edison, Inc. bsmith@h-e.com