> 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
- [HACKERS] foreign key introduces unnecessary locking ? Rini Dutta
- Re: [HACKERS] foreign key introduces unnecessary locki... Stephan Szabo
- RE: [HACKERS] foreign key introduces unnecessary locki... Mikheev, Vadim
- Re: [HACKERS] foreign key introduces unnecessary l... Jan Wieck
- Re: [HACKERS] foreign key introduces unnecessa... Vadim Mikheev
- Vadim Mikheev