Thanks for that pointer David. There was, indeed, a trigger on the table which called a function raising an exception. I just have never seen that prior to this database.
ERROR: Permission denied: UPDATE is not allowed on rhnpackageevr
That doesn't look like a system generated message (and grep on the source tree turns up no results) - which means you should be looking for a trigger that is blocking you.
