Re: foreign key introduces unnecessary locking ? - Mailing list pgsql-hackers

From Vadim Mikheev
Subject Re: foreign key introduces unnecessary locking ?
Date
Msg-id 006c01c03d38$43f58280$b57a30d0@sectorbase.com
Whole thread Raw
In response to Re: foreign key introduces unnecessary locking ?  (Jan Wieck <janwieck@yahoo.com>)
List pgsql-hackers
> 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




pgsql-hackers by date:

Previous
From: "Vadim Mikheev"
Date:
Subject: Re: Re: [COMMITTERS] pgsql/src/test/regress/expected (plpgsql.out inet.out foreign_key.out errors.out)
Next
From: "Horst Herb"
Date:
Subject: Re: [ANNC][RFC] crypto hashes for PostgreSQL 7.0, 7.1