Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit03838b8

Browse files
committed
Fix pg_upgrade to handle event triggers in extensions correctly.
pg_dump with --binary-upgrade must emit ALTER EXTENSION ADD commandsfor all objects that are members of extensions. It forgot to do so forevent triggers, as per bug #15310 from Nick Barnes. Back-patch to 9.3where event triggers were introduced.Haribabu KommiDiscussion:https://postgr.es/m/153360083872.1395.4593932457718151600@wrigleys.postgresql.org
1 parent5b5ed47 commit03838b8

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

‎src/bin/pg_dump/pg_dump.c

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17302,6 +17302,10 @@ dumpEventTrigger(Archive *fout, EventTriggerInfo *evtinfo)
1730217302
appendPQExpBuffer(delqry, "DROP EVENT TRIGGER %s;\n",
1730317303
qevtname);
1730417304

17305+
if (dopt->binary_upgrade)
17306+
binary_upgrade_extension_member(query, &evtinfo->dobj,
17307+
"EVENT TRIGGER", qevtname, NULL);
17308+
1730517309
if (evtinfo->dobj.dump & DUMP_COMPONENT_DEFINITION)
1730617310
ArchiveEntry(fout, evtinfo->dobj.catId, evtinfo->dobj.dumpId,
1730717311
evtinfo->dobj.name, NULL, NULL,

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp