"Marc G. Fournier" <scrappy@postgresql.org> writes:
> On Thu, 11 Aug 2005, Tom Lane wrote:
>> Are you *sure* there are no AFTER triggers here?
>> (Don't forget foreign-key checking triggers.)
> This is all of them ... nothing AFTER, just ON or BEFORE ...
> Foreign-key constraints:
> "xa_classification_id_fk" FOREIGN KEY (classification_id) REFERENCES xa_classification(classification_id) ON
UPDATERESTRICT ON DELETE RESTRICT
> "xa_ip_address_id_fk" FOREIGN KEY (ip_address_id) REFERENCES xa_ip_addresses(ip_address_id) ON UPDATE RESTRICT
ONDELETE RESTRICT
> "xa_logger_status_id_fk" FOREIGN KEY (logger_status_id) REFERENCES xa_logger_status(logger_status_id) ON UPDATE
RESTRICTON DELETE RESTRICT
> "xa_url_queue_id_fk" FOREIGN KEY (url_queue_id) REFERENCES xa_url_queue(url_queue_id) ON UPDATE RESTRICT ON
DELETESET NULL
> Triggers:
> xa_url_domain_b_i_u BEFORE INSERT OR UPDATE ON xa_url FOR EACH ROW EXECUTE PROCEDURE xa_url_domain()
Um, foreign-key triggers are always AFTER.
Can you afford to drop the FK constraints while you do the update? I
can't think of any other short-term workaround.
regards, tom lane
