From: Vadim Mikheev <vmikheev@sectorbase.com>
To: Jan Wieck <janwieck@Yahoo.com>
Cc: 'Rini Dutta' <rinid@rocketmail.com>
Cc: pgsql-sql@hub.org
Cc: pgsql-hackers@hub.org
Cc: Jan Wieck \\(E-mail\\) <janwieck@Yahoo.com>
Subject: Re: foreign key introduces unnecessary locking ?
Date: Mon, 23 Oct 2000 14:29:02 -0700
Message-ID: <006c01c03d38$43f58280$b57a30d0@sectorbase.com> (raw)
References: <200010221226.HAA00859@jupiter.jw.home>
<004f01c03d1e$3430cae0$b67a30d0@sectorbase.com>
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: vmikheev@sectorbase.com, janwieck@Yahoo.com, rinid@rocketmail.com, pgsql-sql@hub.org, pgsql-hackers@hub.org
Subject: Re: foreign key introduces unnecessary locking ?
In-Reply-To: <006c01c03d38$43f58280$b57a30d0@sectorbase.com>
References: <200010221226.HAA00859@jupiter.jw.home> <004f01c03d1e$3430cae0$b67a30d0@sectorbase.com> <006c01c03d38$43f58280$b57a30d0@sectorbase.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox