diff options
| author | Tom Lane | 2018-08-07 19:43:49 +0000 |
|---|---|---|
| committer | Tom Lane | 2018-08-07 19:43:49 +0000 |
| commit | fb4e0e8960e0a58124f6cee1110a9d78fd43674b (patch) | |
| tree | cebb65cb5c8e643137d06482c5111e4bc9e57a6a /src | |
| parent | abd04e0dd8a50d531d6d8e428763a6fc7b16558e (diff) | |
Fix pg_upgrade to handle event triggers in extensions correctly.
pg_dump with --binary-upgrade must emit ALTER EXTENSION ADD commands
for all objects that are members of extensions. It forgot to do so for
event triggers, as per bug #15310 from Nick Barnes. Back-patch to 9.3
where event triggers were introduced.
Haribabu Kommi
Discussion: https://postgr.es/m/153360083872.1395.4593932457718151600@wrigleys.postgresql.org
Diffstat (limited to 'src')
| -rw-r--r-- | src/bin/pg_dump/pg_dump.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/src/bin/pg_dump/pg_dump.c b/src/bin/pg_dump/pg_dump.c index 0c60152eeb7..34cbf6ca640 100644 --- a/src/bin/pg_dump/pg_dump.c +++ b/src/bin/pg_dump/pg_dump.c @@ -14692,6 +14692,10 @@ dumpEventTrigger(Archive *fout, EventTriggerInfo *evtinfo) appendPQExpBuffer(delqry, "DROP EVENT TRIGGER %s;\n", qevtname); + if (binary_upgrade) + binary_upgrade_extension_member(query, &evtinfo->dobj, + "EVENT TRIGGER", qevtname, NULL); + ArchiveEntry(fout, evtinfo->dobj.catId, evtinfo->dobj.dumpId, evtinfo->dobj.name, NULL, NULL, evtinfo->evtowner, false, |