Joe Maldonado <jmaldonado@xxxxxxxxxxxxxxx> writes:
> It seems that TRUNCATE is first posting a lock on the table and then
> waiting for other transactions to finish before truncating the table
> thus blocking all other operations.
That's what it's supposed to do. If you have a problem with the length
of the delay, find the (other) transaction that's accessing the table
for too long and fix that.
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
