Michel Pelletier <pelletier.michel@xxxxxxxxx> writes: > We found the root cause for an issue we encountered restoring a saved > database stored with pg_dumpall, but during this investigation we realized > that pg_dump/all renders `ALTER TABLE` statements for views, for example to > convey ownership. > I get that this is synonymous in most cases, except when there is an event > trigger for `ALTER TABLE`, it ends up firing the event trigger for the > views, and any event triggers expected to fire on `ALTER VIEW` statements > do not fire. > Is this something we can contribute a fix for, or is this some kind of > necessary b/w compat issue that must remain? We're not likely to change the fact that you're allowed to write ALTER TABLE for this, so if your event triggers get broken by doing that you'd best fix the event triggers. I don't have any great objection to making pg_dump emit the more modern spelling (I think ... you'd need to look into pg_restore to make sure it's not assuming something in this area). But doing that won't really remove the hazard. regards, tom lane
