ETP drops cr_item_publish_audit and recreates it to get rid of constraints, citing a bug in PG 7.1. A nasty side effect of the change is that it breaks all CR stored procedures referring to the table (notably content_item__delete). I assume that this is because once compiled, they refer to the table only by its ID, which is rendered useless in this process. This could be looked at as a bug (or at least weakness) in PG, but I wonder what we can do about it from the ACS side. Would it be worth switching the constraints off within the CR create scripts, upping its package version, removing the offending code from ETP and requiring the incremented CR version number? I confess that I don't really know what constraints needed dropping or what the PG 7.1 bug was that made it necessary.
