>
> I'm curious why postgres should be blocking like this, as the foreign key
> constraint is presumably read-based.
No, the foreign key check places an exclusive lock on the parent table's
referenced row.
There's no row level shared lock implemented. This is the problem.
>
> Regards,
> Chris
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>