pgsql: Fix pg_upgrade to handle event triggers in extensions correctly.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix pg_upgrade to handle event triggers in extensions correctly.
Date: 2018-08-07 19:44:09
Message-ID: E1fn7tp-0006Mf-53@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/03838b804905e3fd26ec648c7df1505cf0d8e413

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

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2018-08-07 20:02:06 pgsql: Fix incorrect initialization of BackendActivityBuffer.
Previous Message Tom Lane 2018-08-07 17:14:10 pgsql: Ensure pg_dump_sort.c sorts null vs non-null namespace consisten