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 | 91f6ec2994ff7a86a1bb37c92937c51d07c77422 (patch) | |
| tree | 389ddbda507c0041fc86258b2db3eb5a750ba9a4 /src | |
| parent | f3f6558b5d767317baad6934c6bd0def3bd601bd (diff) | |
| download | postgresql-91f6ec2994ff7a86a1bb37c92937c51d07c77422.tar.gz postgresql-91f6ec2994ff7a86a1bb37c92937c51d07c77422.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 08a9d03138a..d7928e999a2 100644 --- a/src/bin/pg_dump/pg_dump.c +++ b/src/bin/pg_dump/pg_dump.c @@ -15391,6 +15391,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); + ArchiveEntry(fout, evtinfo->dobj.catId, evtinfo->dobj.dumpId, evtinfo->dobj.name, NULL, NULL, evtinfo->evtowner, false, |