Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id DB3B7475D0F for ; Mon, 11 Nov 2002 23:45:44 -0500 (EST) Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by postgresql.org (Postfix) with ESMTP id C9506475A3F for ; Mon, 11 Nov 2002 23:45:41 -0500 (EST) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id gAC4jeo29705; Mon, 11 Nov 2002 23:45:40 -0500 (EST) From: Bruce Momjian Message-Id: <200211120445.gAC4jeo29705@candle.pha.pa.us> Subject: Re: concurrency control docs error In-Reply-To: <87bs4vyg3o.fsf@mailbox.samurai.com> To: Neil Conway Date: Mon, 11 Nov 2002 23:45:40 -0500 (EST) Cc: pgsql-docs@postgresql.org X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200211/17 X-Sequence-Number: 1541 Neil Conway wrote: > The docs on concurrency control & deadlocks (User's Guide, 9.3.3, CVS > docs) state the following: > > Use of explicit locking can cause deadlocks, wherein two (or more) > transactions each hold locks that the other wants. > > This isn't completely true, as deadlocks can occur in applications > that don't use explicit 'LOCK' statements. > > Can someone suggest a better way to phrase the intent of that > statement? But it isn't saying there aren't other deadlock cases, just that explicit locks tend to cause them more frequently. You can add "Often" to the front of the sentence. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073