Received: from postgresql.org.org (webmail.postgresql.org [216.126.85.28]) by postgresql.org (8.11.3/8.11.1) with SMTP id f4BDRJA65332 for ; Fri, 11 May 2001 09:27:19 -0400 (EDT) (envelope-from pgsql-sql-owner@postgresql.org) Received: from news.tht.net (news.hub.org [216.126.91.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f48NurA11623 for ; Tue, 8 May 2001 19:56:53 -0400 (EDT) (envelope-from news@news.tht.net) Received: (from news@localhost) by news.tht.net (8.11.1/8.11.1) id f48NXrE36331 for pgsql-sql@postgresql.org; Tue, 8 May 2001 19:33:53 -0400 (EDT) (envelope-from news) From: "Jack" X-Newsgroups: comp.databases.postgresql.sql Subject: transaction isolation question Date: Wed, 9 May 2001 09:27:16 +1000 Organization: Hub.Org Networking Services (http://www.hub.org) Lines: 7 Message-ID: <9d9vot$13f5$1@news.tht.net> X-Complaints-To: scrappy@hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 To: pgsql-sql@postgresql.org X-Archive-Number: 200105/95 X-Sequence-Number: 2901 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