Deadlock possibility in _bt_check_unique?

Hi,<br />   With the implementation of deferred unique constraints, we need to go back to the index second time to
checkwhether the unique check is valid. Say a situation occurs like this<br />a) the first session doing the unique
checkfinds out that there is a unique check required second time and just makes its entry and comes back<br /> b) the
secondsession doing the unique check finds out that there is a unique check required second time and just makes its
entryand comes back<br /><br />While they do the second check, first session will wait for the session to complete and
viceversa. Won't this result in a deadlock? Isn't this a realistic scenario?<br /><br />Thanks,<br />Gokul.<br />