Received: from bleys.tpgi.com.au (bleys.tpgi.com.au [203.12.160.38]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f4B5XlA31690 for ; Fri, 11 May 2001 01:33:47 -0400 (EDT) (envelope-from quals@bigfoot.com) Received: (from smtpd@localhost) by bleys.tpgi.com.au (8.11.2/8.11.2) id f4B5Xi704618 for ; Fri, 11 May 2001 15:33:44 +1000 Received: from buffy.tpgi.com.au(203.12.160.34) via SMTP by bleys.tpgi.com.au, id smtpdkKyVTz; Fri May 11 15:33:43 2001 Received: (from smtpd@localhost) by buffy.tpgi.com.au (8.9.3/8.9.3) id PAA31145 for ; Fri, 11 May 2001 15:33:42 +1000 Received: from bri2-56k-060.tpgi.com.au(203.29.144.60), claiming to be "hnjack" via SMTP by buffy.tpgi.com.au, id smtpd2qlpXa; Fri May 11 15:33:32 2001 Message-ID: <005901c0d9da$ffb62940$2400a8c0@hnjack> From: "datactrl" To: Subject: Question about Committed Isolation Date: Fri, 11 May 2001 15:26:56 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Archive-Number: 200105/89 X-Sequence-Number: 2890 Regarding "Committed Isolation" on PostgreSql Ver 7.1 Users Guide, is that possible a "Dead Lock" happened when two concurrent transactions are waiting each other? And how to avoid or fix it? Jack