> Is it blocking because orgid is a primary key?
> Does it still block if you use a different orgid in each of the two
> transactions?
It doesn't block if the orgid is different.
Unfortunately that doesn't solve the problem for the actual multiuser
application.
Users are being blocked from adding records or making changes in one table,
while another process has a (long) transaction importing records into
another table.
The two tables are related only by a common foreign key against a third
table.
I'm curious why postgres should be blocking like this, as the foreign key
constraint is presumably read-based.
Regards,
Chris
