Tim Wilson <wilson(at)visi(dot)com> writes:
>> I'd bet on a referential integrity trigger causing the problem. Up till
>> very recently, RENAME TABLE wasn't smart enough to adjust RI trigger
>> parameters. (Don't recall if the fix is in 7.2 or not; it may only be
>> in development sources.)
> So I should drop the 'location_exists' constraint in the 'event' table
> and recreate it?
If it is RI triggers, you'll need to drop the triggers manually ---
there's no support for this in ALTER TABLE :-(. I believe you can
find some discussion of how to do it on techdocs.postgresql.org.
regards, tom lane