Fix pg_dump's handling of event triggers.
authorTom Lane
Sun, 23 Jul 2017 00:20:09 +0000 (20:20 -0400)
committerTom Lane
Sun, 23 Jul 2017 00:20:09 +0000 (20:20 -0400)
commit7debd9f79c98d059f38d524bb242e21433261e1e
treedd1a51d3e0c8261ac0453483809442e778959e88
parented367be64b118bbcda2b4e59fbb44d45c07c80e0
Fix pg_dump's handling of event triggers.

pg_dump with the --clean option failed to emit DROP EVENT TRIGGER
commands for event triggers.  In a closely related oversight,
it also did not emit ALTER OWNER commands for event triggers.
Since only superusers can create event triggers, the latter oversight
is of little practical consequence ... but if we're going to record
an owner for event triggers, then surely pg_dump should preserve it.

Per complaint from Greg Atkins.  Back-patch to 9.3 where event triggers
were introduced.

Discussion: https://postgr.es/m/20170722191142[email protected]
src/bin/pg_dump/pg_backup_archiver.c
src/bin/pg_dump/pg_dump.c