postgres.git / summary / log / commit / refs

commit    fb4e0e8960e0a58124f6cee1110a9d78fd43674b
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Tue Aug 07 19:43:49 2018 +0000
First released in: 12.0, 9.3.25, 9.4.20, 9.5.15, 9.6.11, 10.6, 11.0

    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


 src/bin/pg_dump/pg_dump.c | 4 ++++
 1 file changed, 4 insertions(+)

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,


[parent: abd04e0dd8a5]