Re: [GENERAL] pg_dump dumps EVENT TRIGGER owned by extension

2013-12-31 Thread Michael Paquier
On Tue, Dec 31, 2013 at 5:33 AM, Moshe Jacobson wrote: > > On Mon, Dec 30, 2013 at 2:02 PM, Tom Lane wrote: >> >> I've committed fixes for these > > > Will these fixes appear in 9.3.3? Yes. -- Michael -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to yo

Re: [GENERAL] pg_dump dumps EVENT TRIGGER owned by extension

2013-12-30 Thread Moshe Jacobson
On Mon, Dec 30, 2013 at 2:02 PM, Tom Lane wrote: > I've committed fixes for these Will these fixes appear in 9.3.3? Thanks. Moshe Jacobson Manager of Systems Engineering, Nead Werx Inc. 2323 Cumberland Parkway · Suite 201 · Atlanta, GA 30339 "Quality is not an act

Re: [GENERAL] pg_dump dumps EVENT TRIGGER owned by extension

2013-12-30 Thread Moshe Jacobson
On Mon, Dec 30, 2013 at 2:02 PM, Tom Lane wrote: > 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

Re: [GENERAL] pg_dump dumps EVENT TRIGGER owned by extension

2013-12-30 Thread Tom Lane
Moshe Jacobson 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 rest

Re: [GENERAL] pg_dump dumps EVENT TRIGGER owned by extension

2013-12-30 Thread Tom Lane
Moshe Jacobson 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 rest

[GENERAL] pg_dump dumps EVENT TRIGGER owned by extension

2013-12-30 Thread Moshe Jacobson
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