Tom Lane wrote:
Richard Huxton <[EMAIL PROTECTED]> writes:
Does that mean I'll want to disable triggers while I do this?
Hrm. Right now the code does not fire triggers at all, but that seems wrong. However, I doubt that very many triggers could cope with update events in which the old and new rows have different rowtypes :-(. Any thoughts what to do about that?
If triggers exist, I think we should just throw a warning that triggers will not be fired.
Tom's point about triggers probably not working after the upgrade is a good one though. Is it reasonable to just refuse to act on a table until all triggers are dropped? I'd rather be forced to go through and drop/restore triggers in a script than be surprised later on.
-- Richard Huxton Archonet Ltd
---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
