diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2018-08-07 15:43:49 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2018-08-07 15:43:49 -0400 |
| commit | c9dacdb1c9428c2a021ee4d0a444147f8fcf07ef (patch) | |
| tree | b808e511fe35c868d8083ccb8e48823b87fac840 /src | |
| parent | dc391dacf170593dceef07fc7ea287cb02d09d5d (diff) | |
| download | postgresql-c9dacdb1c9428c2a021ee4d0a444147f8fcf07ef.tar.gz postgresql-c9dacdb1c9428c2a021ee4d0a444147f8fcf07ef.zip | |
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 8080155a957..542f9e950de 100644 --- a/src/bin/pg_dump/pg_dump.c +++ b/src/bin/pg_dump/pg_dump.c @@ -16660,6 +16660,10 @@ dumpEventTrigger(Archive *fout, EventTriggerInfo *evtinfo) appendPQExpBuffer(delqry, "DROP EVENT TRIGGER %s;\n", qevtname); + if (dopt->binary_upgrade) + binary_upgrade_extension_member(query, &evtinfo->dobj, + "EVENT TRIGGER", qevtname, NULL); + if (evtinfo->dobj.dump & DUMP_COMPONENT_DEFINITION) ArchiveEntry(fout, evtinfo->dobj.catId, evtinfo->dobj.dumpId, evtinfo->dobj.name, NULL, NULL, |