pgsql: Fix broken support for event triggers as extension members.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix broken support for event triggers as extension members.
Date: 2013-12-30 19:00:14
Message-ID: E1Vxi4U-0002wC-Kd@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix broken support for event triggers as extension members.

CREATE EVENT TRIGGER forgot to mark the event trigger as a member of its
extension, and pg_dump didn't pay any attention anyway when deciding
whether to dump the event trigger. Per report from Moshe Jacobson.

Given the obvious lack of testing here, it's rather astonishing that
ALTER EXTENSION ADD/DROP EVENT TRIGGER work, but they seem to.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/c01bc51f8d596d425d897c833ef11ca3670ea984

Modified Files
--------------
src/backend/commands/event_trigger.c | 5 ++++-
src/bin/pg_dump/pg_dump.c | 16 ++++++++++++++++
2 files changed, 20 insertions(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Meskes 2014-01-01 12:01:09 pgsql: Do not use an empty hostname.
Previous Message Tom Lane 2013-12-30 18:28:04 pgsql: Fix alphabetization in catalogs.sgml.