"Perry Smith" <[EMAIL PROTECTED]> writes: > Looking at the documentation above, I would expect the insert into A to get a > Row exclusive lock for table A. And, I'm guessing it would get an ACCESS > SHARE lock for table B. But this would not prevent the delete from B from > happening at the same time (if I am reading this correctly).
The bit you quoted was for tables. The RI trigger does indeed take a share lock on the referenced record in table B which prevents it from being deleted. (In older versions it used to take an exclusive lock because there were no share locks on records.) -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
