Received: from mailer.devels.sectorbase.com ([208.48.122.162]) by hub.org (8.10.1/8.11.0) with SMTP id e9NMXVN41441; Mon, 23 Oct 2000 18:33:31 -0400 (EDT) (envelope-from vmikheev@sectorbase.com) Received: from dune (unknown [208.48.122.181]) by mailer.devels.sectorbase.com (Postfix) with SMTP id 532791F735; Mon, 23 Oct 2000 17:22:04 -0400 (EDT) Message-ID: <006c01c03d38$43f58280$b57a30d0@sectorbase.com> From: "Vadim Mikheev" To: "Jan Wieck" Cc: "'Rini Dutta'" , , , "Jan Wieck \\(E-mail\\)" References: <200010221226.HAA00859@jupiter.jw.home> <004f01c03d1e$3430cae0$b67a30d0@sectorbase.com> Subject: Re: foreign key introduces unnecessary locking ? Date: Mon, 23 Oct 2000 14:29:02 -0700 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: 200010/938 X-Sequence-Number: 7980 > Using Dirty transaction removing/updating PK could see that concurrent > xaction attempts to update/insert FK and so would wait for its commit/abort. ^^^^^^^^ Of course this will require some function that would take tid as one of arguments, fetch row and check if someone is updating it. > Just like now same row writers wait for each other. Vadim