Need pg_dump not to dump extension-created triggers

[Moshe Jacobson <moshe@xxxxxxxxxxxx>]

I have an extension which, after installation, creates triggers and their associated functions dynamically and adds the functions to the extension so that they will be dropped with the extension.

However, there is no way to add the trigger to the extension, so pg_dump's output still includes the definition of the trigger, even though it does not include the definition of the corresponding function. This is causing pg_restore to emit warnings on the CREATE TRIGGER commands.

The behavior does not change when I manually insert into pg_depend a dependency from the trigger to the extension.

I'd like to know if the following changes can be made, as I think they will fix this issue:

1. Add command ALTER EXTENSION ... ADD TRIGGER.
2. Modify pg_dump not to dump triggers that are dependent on an extension.

Thanks.

P.S. I'm here at PGCon and will be speaking on Friday about this very extension. Come say hi!

Moshe Jacobson

Manager of Systems Engineering, Nead Werx Inc.

2323 Cumberland Parkway · Suite 201 · Atlanta, GA 30339

"Quality is not an act, it is a habit." -- Aristotle