Re: pg_dump dumps EVENT TRIGGER owned by extension - Mailing list pgsql-general

From Tom Lane
Subject Re: pg_dump dumps EVENT TRIGGER owned by extension
Date
Msg-id 26438.1388430164@sss.pgh.pa.us
Whole thread Raw
In response to pg_dump dumps EVENT TRIGGER owned by extension  (Moshe Jacobson <moshe@neadwerx.com>)
Responses Re: pg_dump dumps EVENT TRIGGER owned by extension  (Moshe Jacobson <moshe@neadwerx.com>)
Re: pg_dump dumps EVENT TRIGGER owned by extension  (Moshe Jacobson <moshe@neadwerx.com>)
List pgsql-general
Moshe Jacobson <moshe@neadwerx.com> writes:
> PostgreSQL 9.3.2
> I created an extension that owns an event trigger.
> When I dump the database, it puts the event trigger into the dump output
> even though it's owned by the extension.
> When I restore the database, the extension creates the event trigger and
> the restore causes errors because the event trigger already exists.

> Is this a bug?

Actually, there seem to be two distinct bugs: CREATE EVENT TRIGGER forgets
to mark the event trigger as a member of its extension, and pg_dump
doesn't pay any attention anyway when deciding whether to dump the event
trigger.  I've committed fixes for these, but if you have an existing
extension that should have an event trigger as member, you'll need to use
ALTER EXTENSION ADD EVENT TRIGGER to clean up the mess.

            regards, tom lane


pgsql-general by date:

Previous
From: Raghavendra
Date:
Subject: Re: what does the error mean?
Next
From: Moshe Jacobson
Date:
Subject: Re: pg_dump dumps EVENT TRIGGER owned by extension