Right, I understand the badness of the situation, but unfortunately the
keys are externally generated and I have no control over them.
So I'm looking for "lock <tablename> in exclusive mode"?
Tom Lane wrote:
Pretty much the only thing you can do about that is to take an exclusive
table-level lock. This is simple but pretty awful for concurrency
(since the lock blocks everyone else from inserting ANY key, not only
the one you are inserting).
Consider using a sequence object to generate the keys, instead.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
